https://fedoraproject.org/wiki/Changes/Python3.8 == Summary == Update the Python stack in Fedora from Python 3.7 to Python 3.8. == Owner == * Name: [[User:Churchyard|Miro Hrončok]] == Detailed Description == We would like to upgrade Python to 3.8 in Fedora 31 thus we are proposing this plan early. See the upstream notes at [https://www.python.org/dev/peps/pep-0569/#features-for-3-8 Features for 3.8] and [https://docs.python.org/3.8/whatsnew/3.8.html What's new in 3.8]. === Important dates and plan === * 2019-02-03 Python 3.8.0 alpha 1 ** Package it as {{package|python38}} for testing purposes ** Start the bootstrap procedure in Copr ** Do a mass rebuild against every future release in Copr * 2019-05-26 Python 3.8.0 beta 1 ** If the Copr mass rebuild results were good, we will push the update to rawhide and do the bootstrapping + mass rebuild in a side tag * , 2019-06-23 Python 3.8.0 beta 2 ** If the side tag bootstrapping and mass rebuild results were good, we will merge it to Fedora at this point * 2019-07-30 expected earliest Fedora 31 mass rebuild * 2019-09-05 expected earliest Fedora 31 beta freeze ** Everything should be well tested on beta 1 to 4 * 2019-09-29 Python 3.8.0 candidate 1 ** (we block Fedora release before we have this) * 2019-10-16 expected earliest Fedora 31 final freeze * 2019-10-20 Python 3.8.0 final ** Gets in with a pre-approved exception (From [https://www.python.org/dev/peps/pep-0569/#schedule Python 3.8 Release Schedule] and [[Releases/31/Schedule|Fedora 31 Release Schedule]].) The schedule is '''very tight''', but the Fedora dates are the earliest estimates. So we are proposing this early, in the case the Fedora schedule might need to be adjusted. Note that upstream's "release candidates" are frozen except for blocker bugs. Since we can and will backport blocker fixes between Fedora and upstream, we essentially treat the Release Candidate as the final release. === Notes from the previous upgrade === There are notes from the previous upgrade available, so this upgrade may go smoother: [[SIGs/Python/UpgradingPython]] == Benefit to Fedora == Fedora aims to showcase the latest in free and open source software - we should have the most recent release of Python 3. Packages in Fedora can use the new features from 3.8. There's also a benefit to the larger Python ecosystem: by building Fedora's packages against 3.8 while it's still in development, we can catch critical bugs before the final 3.8.0 release. == Scope == We will coordinate the work in a side tag and merge when ready. * Proposal owners: *# Introduce {{package|python38}} for all Fedoras *# Prepare stuff in Copr as explained in description. *# Retire {{package|python38}} from F31+ *# Update {{package|python3}} to what was in {{package|python38}} *#* Mass rebuild all the packages that BR {{package|python3}}/{{package|python3-devel}}/... (~2700 listed in [http://fedora.portingdb.xyz/ Python 3 Porting Database for Fedora]) *# Reintroduce {{package|python37}} from Fedora 28. Update it to have all fixes and enhancements from {{package|python3}} in Fedora 30 (or 31 before this change) * Other developers: Maintainers of packages that fail to rebuild during the rebuilds will be asked, using e-mail and bugzilla, to fix or remove their packages from the distribution. If any issues appear, they should be solvable either by communicating with the respective upstreams first and/or applying downstream patches. Also the package maintainers should have a look at: [https://docs.python.org/3.8/whatsnew/3.8.html#porting-to-python-3-8 Porting to Python 3.8]. And python-maint team will be available to help with fixing issues. * Fedora QA: Based on some troubles with the [[Changes/Python3.6|change to 3.6]], we'd like to have an ack from QA before we merge the side tag. We'd also like QA to approve this change. * Release engineering: [https://pagure.io/releng/issue/8092 #8092] A targeted rebuild for all python packages will be required, before the mass rebuild. ** List of deliverables: nope * Policies and guidelines: nope * Trademark approval: nope == Upgrade/compatibility impact == All the packages that depend on Python 3 must be rebuilt. User written Python 3 scripts/applications may require a small amount of porting, but mostly Python 3.7 is forward compatible with Python 3.8. == How To Test == Interested testers do not need special hardware. If you have a favorite Python 3 script, module, or application, please test it with Python 3.8 and verify that it still works as you would expect. You can test it using {{package|python38}} even before this change is implemented, in Fedora 29 or 30. Once the change is in place, test if you favorite Python apps are working as they were before. File bugs if they don't. == User Experience == Regular distro users shouldn't notice any change in system behavior other than the Python 3 interpreter will be in version 3.8. == Dependencies == ~2700 packages depend on {{package|python3}}. See scope section. == Contingency Plan == * Contingency mechanism: Do not merge the side tag with rawhide. If the side tag has been merged and issues arise, that will justify a downgrade, then use an epoch tag to revert to 3.7 version (never needed before) * Contingency deadline: TBD * Blocks release? Yes, we'd like to block Fedora 31 release on at least 3.8.0 rc 1 * Blocks product? See above == Documentation == [https://www.python.org/dev/peps/pep-0569/ Python 3.8 Release Schedule] [https://www.python.org/dev/peps/pep-0569/#features-for-3-8 Features for 3.8] [https://docs.python.org/3.8/whatsnew/3.8.html What's new in 3.8] [https://docs.python.org/3.8/whatsnew/3.8.html#porting-to-python-3-8 Porting to Python 3.8] -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
