From Fedora Project Wiki
< Changes
Churchyard (talk | contribs) (releng ticket) |
Churchyard (talk | contribs) m (Document the pc linker thing) |
||
| (23 intermediate revisions by 5 users not shown) | |||
| Line 22: | Line 22: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
= Python 3.8 <!-- The name of your change proposal --> = | = Python 3.8 <!-- The name of your change proposal --> = | ||
{{admon/important|Deferred to Fedora 32|This change was originally proposed for [[Releases/31|Fedora 31]], but has been deferred to [[Releases/32|Fedora 32]].}} | |||
== Summary == | == Summary == | ||
Update the Python | Update the Python stack in Fedora from Python 3.7 to Python 3.8. | ||
== Owner == | == Owner == | ||
| Line 45: | Line 47: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/32|Fedora 32]] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 55: | Line 57: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1686977 #1686977] | ||
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/310 #310] | |||
== Detailed Description == | == Detailed Description == | ||
We | We would like to upgrade Python to 3.8 in <del>Fedora 31</del> Fedora 32 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]. | 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 === | === Important dates and plan (updated for Fedora 32) === | ||
* 2019-02-03 Python 3.8.0 alpha 1 | * 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- | * 2019-06-04 Python 3.8.0 beta 1 (was: 2019-05-27) | ||
** | * 2019-07-04 Python 3.8.0 beta 2 (was: 2019-07-01) | ||
* | * <del>2019-07-24 expected Fedora 31 mass rebuild</del> | ||
** | * 2019-07-29 Python 3.8.0 beta 3 | ||
** 2019- | * 2019-08-13 expected Fedora 31 branching (Rawhide becomes future Fedora 32) | ||
** after branching, we can start building in Fedora 32 side tag | |||
* 2019-09- | * 2019-08-21 The side tag was merged | ||
* | * 2019-08-26 Python 3.8.0 beta 4 | ||
* 2019-10- | * <del>2019-08-29 expected Fedora 31 beta freeze</del> | ||
* 2019-10- | * 2019-09-30 Python 3.8.0 candidate 1 | ||
** | * 2019-10-07 Python 3.8.0 candidate 2 (if necessary) | ||
* <del>2019-10-08 expected Fedora 31 final freeze</del> | |||
* 2019-10-21 Python 3.8.0 final | |||
* 2020-01-24 expected Fedora 32 mass rebuild | |||
** gives us about 3 months between side tag merge and mass rebuild | |||
* 2020-02-29 expected Fedora 32 beta freeze | |||
** gives us about 4 months between side tag merge and beta freeze | |||
** chances are, 3.8.1 is already out at this point | |||
(From [https://www.python.org/dev/peps/pep-0569/#schedule Python 3.8 Release Schedule] and [[Releases/31/Schedule|Fedora 31 Release Schedule]].) | (From [https://www.python.org/dev/peps/pep-0569/#schedule Python 3.8 Release Schedule] and [[Releases/31/Schedule|Fedora 31 Release Schedule]] ([[Releases/32/Schedule|Fedora 32 Release Schedule]] is not yet available).) | ||
The schedule is '''very tight''' | <del>The schedule is '''very tight''' for Fedora 31. So we are proposing this early, in the case the Fedora schedule might need to be adjusted.</del> | ||
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 === | === Notes from the previous upgrade === | ||
| Line 93: | Line 105: | ||
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. | 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. | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | ||
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 == | == Scope == | ||
| Line 101: | Line 115: | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
*# Introduce {{package|python38}} for all Fedoras | *# Introduce {{package|python38}} for all Fedoras | ||
*# | *# Prepare stuff in Copr as explained in description. | ||
*# Retire {{package|python38}} from | *# Retire {{package|python38}} from F32+ | ||
*# Update {{package|python3}} to what was in {{package|python38}} | *# Update {{package|python3}} to what was in {{package|python38}} | ||
*#* Mass rebuild all the packages that BR {{package|python3}}/{{package|python3-devel}}/... (~ | *#* Mass rebuild all the packages that BR {{package|python3}}/{{package|python3-devel}}/... (~3000 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 | *# Reintroduce {{package|python37}} from Fedora 28. Update it to have all fixes and enhancements from {{package|python3}} in Fedora 31 (or 32 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: [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. | * 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. | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 147: | Line 161: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
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. | 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. If the application you are testing does not require any other modules, 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 | In case your application requires other modules, or if you are testing an rpm package, it is necessary to install the 3.8 version of the python3 rpm. Right now that rpm is available in copr, along with all other python packages that build successfully with python 3.8. See https://copr.fedorainfracloud.org/coprs/g/python/python3.8/ for detailed instructions how to enable Python 3.8 copr for mock. | ||
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 == | == User Experience == | ||
| Line 169: | Line 185: | ||
* Contingency deadline: TBD <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: TBD <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? Yes, we'd like to block Fedora | * Blocks release? Yes, we'd like to block Fedora 32 release on at least 3.8.0rc1 <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product? See above <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | * Blocks product? See above <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | ||
| Line 190: | Line 206: | ||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | ||
--> | --> | ||
Note: Make sure to document this: https://bugzilla.redhat.com/show_bug.cgi?id=1812598 | |||
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/XXX #XXX] | * Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/XXX #XXX] | ||
[[Category: | [[Category:ChangeAcceptedF32]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 17:26, 11 March 2020
Python 3.8
Summary
Update the Python stack in Fedora from Python 3.7 to Python 3.8.
Owner
- Name: Miro Hrončok
- Email: python-maint@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 32
- Last updated: 2020-03-11
- Tracker bug: #1686977
- Release notes tracker: #310
Detailed Description
We would like to upgrade Python to 3.8 in Fedora 31 Fedora 32 thus we are proposing this plan early.
See the upstream notes at Features for 3.8 and What's new in 3.8.
Important dates and plan (updated for Fedora 32)
- 2019-02-03 Python 3.8.0 alpha 1
- Package it as
python38 - Start the bootstrap procedure in Copr
- Do a mass rebuild against every future release in Copr
- Package it as
- 2019-06-04 Python 3.8.0 beta 1 (was: 2019-05-27)
- 2019-07-04 Python 3.8.0 beta 2 (was: 2019-07-01)
2019-07-24 expected Fedora 31 mass rebuild- 2019-07-29 Python 3.8.0 beta 3
- 2019-08-13 expected Fedora 31 branching (Rawhide becomes future Fedora 32)
- after branching, we can start building in Fedora 32 side tag
- 2019-08-21 The side tag was merged
- 2019-08-26 Python 3.8.0 beta 4
2019-08-29 expected Fedora 31 beta freeze- 2019-09-30 Python 3.8.0 candidate 1
- 2019-10-07 Python 3.8.0 candidate 2 (if necessary)
2019-10-08 expected Fedora 31 final freeze- 2019-10-21 Python 3.8.0 final
- 2020-01-24 expected Fedora 32 mass rebuild
- gives us about 3 months between side tag merge and mass rebuild
- 2020-02-29 expected Fedora 32 beta freeze
- gives us about 4 months between side tag merge and beta freeze
- chances are, 3.8.1 is already out at this point
(From Python 3.8 Release Schedule and Fedora 31 Release Schedule (Fedora 32 Release Schedule is not yet available).)
The schedule is very tight for Fedora 31. 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
- Prepare stuff in Copr as explained in description.
- Retire
- Update
- Mass rebuild all the packages that BR
- Mass rebuild all the packages that BR
- Reintroduce
- Introduce
- 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: 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: #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. If the application you are testing does not require any other modules, you can test it using 
python38
In case your application requires other modules, or if you are testing an rpm package, it is necessary to install the 3.8 version of the python3 rpm. Right now that rpm is available in copr, along with all other python packages that build successfully with python 3.8. See https://copr.fedorainfracloud.org/coprs/g/python/python3.8/ for detailed instructions how to enable Python 3.8 copr for mock.
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
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 32 release on at least 3.8.0rc1
- Blocks product? See above
Documentation
Release Notes
Note: Make sure to document this: https://bugzilla.redhat.com/show_bug.cgi?id=1812598
- Release Notes tracking: #XXX