[Python-modules-team] Bug#955059: django-tables: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info'

[Lucas Nussbaum]

Source: django-tables
Version: 2.1.1-1
Severity: important
Tags: ftbfs
User: python-modules-team at lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

django-tables fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> PYTHONPATH=. python3 -m sphinx -b html -d docs/.build/.doctrees -N docs docs/.build/html
> Running Sphinx v2.4.3
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinxcontrib/spelling/__init__.py", line 11, in setup
>     app.info('Initializing Spelling Checker')
> AttributeError: 'Sphinx' object has no attribute 'info'
> The full traceback has been saved in /tmp/sphinx-err-1ajeylsn.log, if you want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error message can be provided next time.
> A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/03/26/django-tables_2.1.1-1_unstable_sphinx243.log

Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.

Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.

Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.

In case you have questions, please Cc sphinx at packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/2.0/changes.html
[2]: https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.