Le 2021-01-13 à 00:28, Victor Stinner a écrit : > Since documentation changes are backported to 3.8 and 3.9 stable > branches, if we increase the minimum required Sphinx version in > master, I would prefer to also increase it in 3.8 and 3.9 branches.
Bumping a dependency on the next release is already hard, I don't think we can bump dependencies on current releases like Python 3.8. > I would prefer to not have to check manually if a doc backport PR is > still compatible with Sphinx 2 or not. As we're using `-W` flag of sphinx-build, the tests would spot it and mark the backport PR as not mergeable. The doc would diverge from a branch to another, but it already does, so I do not worry a lot about conflicts. > The alternative is to keep Sphinx 2 support, use > strip_signature_backslash and don't use :no-trim-doctest-flags: ? Exact, totally doable for a few years to ease the migration, we could even keep Sphinx 1.8 support for a few years as it still works with those two "fixes" applied (it would imply reopening https://bugs.python.org/issue36675 but I'm not against it). -- [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/E77DZXH4JCQS2Y2TGUHW7QB2Q546SJCI/ Code of Conduct: http://python.org/psf/codeofconduct/
