- 1 Python 3.8
- 1.1 Summary
- 1.2 Owner
- 1.3 Current status
- 1.4 Detailed Description
- 1.5 Benefit to Fedora
- 1.6 Scope
- 1.7 Upgrade/compatibility impact
- 1.8 How To Test
- 1.9 User Experience
- 1.10 Dependencies
- 1.11 Contingency Plan
- 1.12 Documentation
- 1.13 Release Notes
Update the Python 3 stack in Fedora from Python 3.7 to Python 3.8.
- Name: Miro Hrončok
- Email: firstname.lastname@example.org
- Release notes owner:
- Targeted release: Fedora 31
- Last updated: 2019-01-31
- Tracker bug: <will be assigned by the Wrangler>
We want to upgrade Python to 3.8 in Fedora 31 and we propose this plan early.
Important dates and plan
- 2019-02-03 Python 3.8.0 alpha 1
- 2019-05-26 Python 3.8.0 beta 1
- if Copr was good, we push to rawhide and bootstrap + mass rebuild in a side tag
- , 2019-06-23 Python 3.8.0 beta 2
- if side tag was good, we merge it to Fedora at this point
- 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 an pre approved exception
The schedule is very tight, but the Fedora dates are the earliest expectations. So we propose this early and the Fedora schedule might get adjusted.
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.
We will coordinate the work in a side tag and merge when ready.
- Proposal owners:
for all Fedoras
- Prep stuff in Copr as explained in description.
to what was in
- Mass rebuild all the packages that BR
/... (~2700 listed in Python 3 Porting Database for Fedora)
- Mass rebuild all the packages that BR
from Fedora 28. Update it to have all fixes and enhancements from
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 upstreams first and/or applying downstream patches. Also the package maintainers should have a look at: 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 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: #XXX 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
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 expect. You can test it using
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 bugzillas if they don't.
Regular distro users shouldn't notice any change in system behavior other than the Python 3 interpreter will be in version 3.8.
- 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
- Release Notes tracking: #XXX