From Fedora Project Wiki
< Changes
Churchyard (talk | contribs) (Copy the Python 3.8 change) |
Churchyard (talk | contribs) |
||
| (23 intermediate revisions by 3 users not shown) | |||
| Line 21: | Line 21: | ||
<!-- 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. | = Python 3.9 <!-- The name of your change proposal --> = | ||
== Summary == | == Summary == | ||
Update the Python stack in Fedora from Python 3. | Update the Python stack in Fedora from Python 3.8 to Python 3.9. | ||
== Owner == | == Owner == | ||
| Line 34: | Line 32: | ||
--> | --> | ||
* Name: [[User:Churchyard|Miro Hrončok]] | * Name: [[User:Churchyard|Miro Hrončok]] | ||
* Name: [[User:Cstratak|Charalampos Stratakis]] | |||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
| Line 47: | Line 46: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/33 | Fedora 33 ]] | ||
* 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 | ||
Bugzilla states meaning as usual: | Bugzilla states meaning as usual: | ||
ASSIGNED -> accepted by FESCo with on going development | ASSIGNED -> accepted by FESCo with on going development | ||
MODIFIED -> change is substantially done and testable | MODIFIED -> change is substantially done and testable | ||
| Line 57: | Line 55: | ||
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: [https://bugzilla.redhat.com/show_bug.cgi?id= | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1785415 #1785415] | ||
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/ | * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/424 #424] | ||
== Detailed Description == | == Detailed Description == | ||
We would like to upgrade Python to 3. | We would like to upgrade Python to 3.9 in Fedora 33 thus we are proposing this plan early. | ||
See the upstream notes at [https://www.python.org/dev/peps/pep- | See the upstream notes at [https://www.python.org/dev/peps/pep-0596/#features-for-3-9 Features for 3.9] and [https://docs.python.org/3.9/whatsnew/3.9.html What's new in 3.9]. | ||
=== Important dates and plan | === Important dates and plan === | ||
* 2019- | * 2019-06-04: Python 3.9 development begins | ||
** Package it as {{package| | * 2019-11-19: Python 3.9.0 alpha 1 | ||
** Package it as {{package|python3.9}} for testing purposes | |||
** Start the bootstrap procedure in Copr | ** Start the bootstrap procedure in Copr | ||
** Do a mass rebuild against every future release in Copr | ** Do a mass rebuild against every future release in Copr | ||
* 2019- | * 2019-12-18: Python 3.9.0 alpha 2 | ||
* | * 2020-01-25: Python 3.9.0 alpha 3 | ||
* | * 2020-02-11: Branch Fedora 32, Rawhide becomes future Fedora 33 | ||
* | ** The earliest point when we can start rebuilding in Koji side-tag | ||
* | * 2020-02-26: Python 3.9.0 alpha 4 | ||
** | * 2020-03-23: Python 3.9.0 alpha 5 | ||
* | * 2020-04-28: Python 3.9.0 alpha 6 | ||
* | * 2020-05-18: Python 3.9.0 beta 1 | ||
* | ** No new features beyond this point | ||
* | ** The ideal point when we can start rebuilding in Koji | ||
* | * 2020-05-29: Actual side tag-merge | ||
* | * 2020-05-30: Expected side tag-merge (optimistic) | ||
* | * 2020-06-09: Python 3.9.0 beta 2/3 | ||
* 2020- | * 2020-06-18: Expected side tag-merge (realistic) | ||
** | * 2020-06-29: Python 3.9.0 beta 4 | ||
* 2020- | * 2020-07-18: Expected side tag-merge (pessimistic) | ||
* | * 2020-07-20: Python 3.9.0 beta 5 | ||
* 2020-07-22: Fedora 33 Mass Rebuild | |||
** The mass rebuild happens with fifth beta. We might need to rebuild Python packages later in exceptional case. | |||
** If the Koji side-tag is not merged yet at this point, we defer the change to Fedora 34. | |||
* 2020-08-10: Python 3.9.0 candidate 1 | |||
** This serves as "final" for our purposes. | |||
* 2020-08-11: Branch Fedora 33, Rawhide becomes future Fedora 34 | |||
* 2020-08-11: Fedora 33 Change Checkpoint: Completion deadline (testable) | |||
* 2020-08-25: Fedora Beta Freeze | |||
** If rebuild with 3.9.0rc1 is needed, we should strive to do it before the freeze - there is a window of 2 weeks. | |||
* 2020-09-14: Python 3.9.0 candidate 2 | |||
* 2020-09-15: Fedora 33 Beta Release (Preferred Target) | |||
** Beta will likely be released with 3.9.0rc1. | |||
* 2020-09-22: Fedora 33 Beta Target date #1 | |||
* 2020-10-05: Python 3.9.0 final | |||
* 2020-10-06: Fedora 33 Final Freeze | |||
** We'll update to 3.9.0 final using a freeze exception. | |||
* 2020-10-20: Fedora 33 Preferred Final Target date | |||
* 2020-10-27: Fedora 33 Final Target date #1 | |||
(From [https://www.python.org/dev/peps/pep-0596/#schedule Python 3.9 Release Schedule] and [https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html Fedora 33 Release Schedule].) | |||
The schedule is somewhat tight for Fedora 33, but Python's [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/AKA3USBKFYKUQDSGDK4FNDYYWMKM7XKX/ annual release cycle was adapted for Fedora], hence we have a better chance of making it in time. In the future, it is expected that Python will be upgraded on a similar schedule in every odd-numbered Fedora release. | |||
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. | 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. | ||
| Line 103: | Line 120: | ||
== Benefit to Fedora == | == 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. | 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.9. | ||
<!-- 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. | There's also a benefit to the larger Python ecosystem: by building Fedora's packages against 3.9 while it's still in development, we can catch critical bugs before the final 3.9.0 release. | ||
== Scope == | == Scope == | ||
| Line 114: | Line 131: | ||
* Proposal owners: | * Proposal owners: | ||
<!-- 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| | *# Introduce {{package|python3.9}} for all Fedoras | ||
*# Prepare stuff in Copr as explained in description. | *# Prepare stuff in Copr as explained in description. | ||
*# Retire {{package| | *# Retire {{package|python3}} from F33+ | ||
*# Update | *# Update {{package|python-rpm-macros}} so {{package|python3.9}} builds {{package|python3}} | ||
*# | *# 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| | *# Reintroduce {{package|python3.8}} from Fedora 31. Update it to have all fixes and enhancements from {{package|python3}} in Fedora 32 (or 33 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. | * 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.9/whatsnew/3.9.html#porting-to-python-3-9 Porting to Python 3.9]. The 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?--> | ||
* Release engineering: [https://pagure.io/releng/issue/9046 #9046] <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES --> A targeted rebuild for all python packages will be required, before the mass rebuild. | |||
* Release engineering: [https://pagure.io/releng/issue/ | |||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
| Line 142: | Line 157: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
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. | 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.8 is forward compatible with Python 3.9. | ||
== How To Test == | == How To Test == | ||
| Line 161: | Line 176: | ||
<!-- 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. | Interested testers do not need special hardware. If you have a favorite Python 3 script, module, or application, please test it with Python 3.9 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|python3.9}} even before this change is implemented, in Fedora 30, 31 or 32. | ||
In case your application requires other modules, or if you are testing an rpm package, it is necessary to install the 3. | In case your application requires other modules, or if you are testing an rpm package, it is necessary to install the 3.9 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.9. See https://copr.fedorainfracloud.org/coprs/g/python/python3.9/ for detailed instructions how to enable Python 3.9 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. | Once the change is in place, test if you favorite Python apps are working as they were before. File bugs if they don't. | ||
| Line 170: | Line 185: | ||
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Regular distro users shouldn't notice any change in system behavior other than the Python 3 interpreter will be in version 3. | Regular distro users shouldn't notice any change in system behavior other than the Python 3 interpreter will be in version 3.9. | ||
== Dependencies == | == Dependencies == | ||
| Line 176: | Line 191: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
3000+ packages depend on {{package|python3}}. See scope section. | |||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* 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. | * 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.8 version (never needed before) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* 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 33 release on at least 3.9.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 192: | Line 207: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
[https://www.python.org/dev/peps/pep- | [https://www.python.org/dev/peps/pep-0596/ Python 3.9 Release Schedule] | ||
[https://www.python.org/dev/peps/pep- | [https://www.python.org/dev/peps/pep-0596/#features-for-3-9 Features for 3.9] | ||
[https://docs.python.org/3. | [https://docs.python.org/3.9/whatsnew/3.9.html What's new in 3.9] | ||
[https://docs.python.org/3. | [https://docs.python.org/3.9/whatsnew/3.9.html#porting-to-python-3-9 Porting to Python 3.9] | ||
== Release Notes == | == Release Notes == | ||
| Line 207: | Line 222: | ||
--> | --> | ||
* | * Migrating user installed packages - https://pagure.io/fedora-docs/release-notes/issue/503 | ||
[[Category: | [[Category:ChangeAcceptedF33]] | ||
<!-- 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 08:06, 21 October 2020
Python 3.9
Summary
Update the Python stack in Fedora from Python 3.8 to Python 3.9.
Owner
- Name: Miro Hrončok
- Name: Charalampos Stratakis
- Email: python-maint@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 33
- Last updated: 2020-10-21
- Tracker bug: #1785415
- Release notes tracker: #424
Detailed Description
We would like to upgrade Python to 3.9 in Fedora 33 thus we are proposing this plan early.
See the upstream notes at Features for 3.9 and What's new in 3.9.
Important dates and plan
- 2019-06-04: Python 3.9 development begins
- 2019-11-19: Python 3.9.0 alpha 1
- Package it as
python3.9 - Start the bootstrap procedure in Copr
- Do a mass rebuild against every future release in Copr
- Package it as
- 2019-12-18: Python 3.9.0 alpha 2
- 2020-01-25: Python 3.9.0 alpha 3
- 2020-02-11: Branch Fedora 32, Rawhide becomes future Fedora 33
- The earliest point when we can start rebuilding in Koji side-tag
- 2020-02-26: Python 3.9.0 alpha 4
- 2020-03-23: Python 3.9.0 alpha 5
- 2020-04-28: Python 3.9.0 alpha 6
- 2020-05-18: Python 3.9.0 beta 1
- No new features beyond this point
- The ideal point when we can start rebuilding in Koji
- 2020-05-29: Actual side tag-merge
- 2020-05-30: Expected side tag-merge (optimistic)
- 2020-06-09: Python 3.9.0 beta 2/3
- 2020-06-18: Expected side tag-merge (realistic)
- 2020-06-29: Python 3.9.0 beta 4
- 2020-07-18: Expected side tag-merge (pessimistic)
- 2020-07-20: Python 3.9.0 beta 5
- 2020-07-22: Fedora 33 Mass Rebuild
- The mass rebuild happens with fifth beta. We might need to rebuild Python packages later in exceptional case.
- If the Koji side-tag is not merged yet at this point, we defer the change to Fedora 34.
- 2020-08-10: Python 3.9.0 candidate 1
- This serves as "final" for our purposes.
- 2020-08-11: Branch Fedora 33, Rawhide becomes future Fedora 34
- 2020-08-11: Fedora 33 Change Checkpoint: Completion deadline (testable)
- 2020-08-25: Fedora Beta Freeze
- If rebuild with 3.9.0rc1 is needed, we should strive to do it before the freeze - there is a window of 2 weeks.
- 2020-09-14: Python 3.9.0 candidate 2
- 2020-09-15: Fedora 33 Beta Release (Preferred Target)
- Beta will likely be released with 3.9.0rc1.
- 2020-09-22: Fedora 33 Beta Target date #1
- 2020-10-05: Python 3.9.0 final
- 2020-10-06: Fedora 33 Final Freeze
- We'll update to 3.9.0 final using a freeze exception.
- 2020-10-20: Fedora 33 Preferred Final Target date
- 2020-10-27: Fedora 33 Final Target date #1
(From Python 3.9 Release Schedule and Fedora 33 Release Schedule.)
The schedule is somewhat tight for Fedora 33, but Python's annual release cycle was adapted for Fedora, hence we have a better chance of making it in time. In the future, it is expected that Python will be upgraded on a similar schedule in every odd-numbered Fedora release.
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.9.
There's also a benefit to the larger Python ecosystem: by building Fedora's packages against 3.9 while it's still in development, we can catch critical bugs before the final 3.9.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
- 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.9. The python-maint team will be available to help with fixing issues.
- Release engineering: #9046 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.8 is forward compatible with Python 3.9.
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.9 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 
python3.9
In case your application requires other modules, or if you are testing an rpm package, it is necessary to install the 3.9 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.9. See https://copr.fedorainfracloud.org/coprs/g/python/python3.9/ for detailed instructions how to enable Python 3.9 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.9.
Dependencies
3000+ 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.8 version (never needed before)
- Contingency deadline: TBD
- Blocks release? Yes, we'd like to block Fedora 33 release on at least 3.9.0rc1
- Blocks product? See above
Documentation
Release Notes
- Migrating user installed packages - https://pagure.io/fedora-docs/release-notes/issue/503