Le 2021-01-13 à 00:09, Senthil Kumaran a écrit : > Wouldn't this a bug with Sphinx?
No, this is a documented breaking change between Sphinx 2 and Sphinx 3. > Why would that be special cased with a flag (strip_signature_backslash)? The strip_signature_backslash has been introduced to allow Sphinx 3 to behave like Sphinx 2 in respect of backslash in signatures. It would allow us to write Sphinx 2 and Sphinx 3 compatible doc. > I noticed that you suggested not to backport this PR > https://github.com/python/cpython/pull/24142 I'm against changing the major version of the Sphinx we use during the life of a release. It looks already hard for distrib maintainers to handle a Sphinx upgrade for the next release, let's not upgrade it on live releases. In other words: it may or may not be OK to bump Sphinx for a minor Python release, but it's clearly not for a patch release (only my point of view). > * Would that mean we have to careful not to use/merge sphinx features like > `no-trim-doctest-flags` to older docs? Exactly: backporting a Doc commit could not work, but it would be spotted by the tests and not mergeable, as we use `-W` flag of Sphinx build (treat warnings as errors). > * What would it take to keep all active versions of Cpython docs build at the > same min version (possibly 3.2)? As said previously, I don't think it's OK to bump Python 3.7 to use Sphinx 3 now. > As Cpython developer, I see nothing bad, but platform maintainers seem to have > some concerns, and it will be good to see points against this. That's exactly why I opened this thread, if it's OK for all platform maintainers, we'll do this, but if not, we can revert a few commits and postpone the Sphinx upgrade, no worries. -- [Julien Palard](https://mdk.fr) _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/W5QVYL5L4DMA2BR5J5NNWRJ2KDMRNGX7/ Code of Conduct: http://python.org/psf/codeofconduct/
