[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#963647: elpy: FTBFS with Sphinx 3.1: Could not import extension elispdomain (exception: cannot import name 'l_' from 'sphinx.locale' (/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))



Control: forwarded -1 https://github.com/jorgenschaefer/elpy/issues/1816

Lucas Nussbaum <lucas@debian.org> writes:

> Source: elpy
> Version: 1.34.0-1
> Severity: important
> Tags: ftbfs
> User: python-modules-team@lists.alioth.debian.org
> Usertags: sphinx3.1
>
> Hi,
>
> elpy fails to build with Sphinx 3.1, currently available in
> experimental.
>
> Relevant part (hopefully):
[snip]
>> Running Sphinx v3.1.1
>> 
>> Extension error:
>> Could not import extension elispdomain (exception: cannot import name 'l_' from 'sphinx.locale' (/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))
>> make[1]: *** [debian/rules:22: override_dh_auto_build] Error 2
>
[snip]
> Sphinx 3.1 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@packages.debian.org on reply.
>

Sphinx 3.0 removed sphinx.locale.l_() for sphinx.locale._() and/or
sphinx.locale.__().  I've forwarded the issue upstream, because I don't
believe I'll have time to check all of their documentation for other
Sphinx 1.x vestiges.

I wasn't able to find a migration doc, mention of sphinx.locale.l_()
appears to have been cut (by upstream) from 1.8.4's docs...this seems
strange and user-hostile, especially for documentation-related
software.

Is a migration doc available somewhere?  In this case I feel like I
wasn't able to assess if it's something I could handle myself (in the
time I am free), due to lack of documentation.

Regards,
Nicholas

Attachment: signature.asc
Description: PGP signature


Reply to: