➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients corona10, mdk, vstinner
Date 2021-01-12.16:38:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1610469487.84.0.197122676186.issue42843@roundup.psfhosted.org>
In-reply-to
Content 
* Fedora 33 (stable) ships python3-sphinx 3.2.1-1 and python3.10 version 3.10.0~a3-1 (the alpha4 is under tests).
* Debian Buster (stable) ships python3-sphinx 1.8.4-1 and python3 version 3.7.3-1
* Debian Sid (unstable) ships python3-sphinx 3.4.3-1 and python3 version 3.9.1-1.
* Ubuntu Groovy (stable) ships python3-sphinx 3.2.1-1 and python3 version 3.8.6-0ubuntu1
* Ubuntu Hirsute (dev) ships python3-sphinx 3.3.1-1 and python3 version 3.9.0-3ubuntu1

In this list, requiring Sphinx 3.2+ to build Python 3.10 documentation would only be an issue on Debian Buster.

I didn't check Red Hat RHEL or SUSE SLE. If they want to ship Python 3.10 but only have an old Sphinx, they can either use a newer Sphinx to build the doc, or ship Python 3.10 with no doc (since it would not be the "system Python", it may be an acceptable tradeoff).
History
Date User Action Args
2021-01-12 16:38:07vstinnersetrecipients: + vstinner, mdk, corona10
2021-01-12 16:38:07vstinnersetmessageid: <1610469487.84.0.197122676186.issue42843@roundup.psfhosted.org>
2021-01-12 16:38:07vstinnerlinkissue42843 messages
2021-01-12 16:38:07vstinnercreate