From Fedora Project Wiki
No edit summary
 
(9 intermediate revisions by 4 users not shown)
Line 23: Line 23:


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF37]]
<!-- 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 -->
Line 41: Line 41:
ON_QA -> change is fully code complete
ON_QA -> change is fully code complete
-->
-->
* FESCo issue: <will be assigned by the Wrangler>
* FESCo issue: [https://pagure.io/fesco/issue/2677 #2677]
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2016048 #2016048]
* Release notes tracker: <will be assigned by the Wrangler>
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/746 #746]


== Detailed Description ==
== Detailed Description ==
Line 63: Line 63:
* 2022-01-03: Python 3.11.0 alpha 4
* 2022-01-03: Python 3.11.0 alpha 4
* 2022-02-02: Python 3.11.0 alpha 5
* 2022-02-02: Python 3.11.0 alpha 5
* [2022-02-09]: Branch Fedora 36, Rawhide becomes future Fedora 37
* 2022-02-08: Branch Fedora 36, Rawhide becomes future Fedora 37
** The earliest point when we can start rebuilding in Koji side-tag
** The earliest point when we can start rebuilding in Koji side-tag
* 2022-02-28: Python 3.11.0 alpha 6
* 2022-02-28: Python 3.11.0 alpha 6
Line 69: Line 69:
* 2022-05-06: Python 3.11.0 beta 1
* 2022-05-06: Python 3.11.0 beta 1
** No new features beyond this point
** No new features beyond this point
* 2022-05-30: Python 3.10.0 beta 2
* 2022-05-30: Python 3.11.0 beta 2
** The ideal point when we can start rebuilding in Koji
** The ideal point when we can start rebuilding in Koji
* 2022-06-06: Expected side tag-merge (optimistic)
* 2022-06-06: Expected side tag-merge (optimistic)
Line 76: Line 76:
* 2022-07-09: Python 3.11.0 beta 4
* 2022-07-09: Python 3.11.0 beta 4
* 2022-07-18: Expected side tag-merge (pessimistic)
* 2022-07-18: Expected side tag-merge (pessimistic)
* [2022-07-21]: Fedora 37 Mass Rebuild
* 2022-07-20: Fedora 37 Mass Rebuild
** The mass rebuild happens with the fourth beta. We might need to rebuild Python packages later in exceptional case.
** The mass rebuild happens with the fourth 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 38.
** If the Koji side-tag is not merged yet at this point, we defer the change to Fedora 38.
* 2022-08-01: Python 3.11.0 candidate 1
* 2022-08-01: Python 3.11.0 candidate 1
** This serves as "final" for our purposes.
** This serves as "final" for our purposes.
* [2022-08-10]: Branch Fedora 37, Rawhide becomes future Fedora 38
* 2022-08-09: Branch Fedora 37, Rawhide becomes future Fedora 38
* [2022-08-10]: Fedora 37 Change Checkpoint: Completion deadline (testable)
* 2022-08-09: Fedora 37 Change Checkpoint: Completion deadline (testable)
* [2022-08-24]: Fedora Beta Freeze
* 2022-08-23: Fedora Beta Freeze
** If rebuild with 3.11.0rc1 is needed, we should strive to do it before the freeze - there is a window of 3 weeks.
** If rebuild with 3.11.0rc1 is needed, we should strive to do it before the freeze - there is a window of 3 weeks.
* 2022-09-05: Python 3.11.0 candidate 2
* 2022-09-05: Python 3.11.0 candidate 2
* [2022-09-19]: Fedora 37 Beta Release (Preferred Target)
* 2022-09-13: Fedora 37 Beta Release (Preferred Target)
** Beta will likely be released with 3.11.0rc2.
** Beta will likely be released with 3.11.0rc2.
* [2022-09-21]: Fedora 37 Beta Target date #1
* 2022-09-20: Fedora 37 Beta Target date #1
* 2022-10-03: Python 3.11.0 final
* 2022-10-03: Python 3.11.0 final
* [2022-10-05]: Fedora 37 Final Freeze
* 2022-10-04: Fedora 37 Final Freeze
** We'll update to 3.11.0 final using a freeze exception.
** We'll update to 3.11.0 final using a freeze exception.
* [2022-10-19]: Fedora 37 Preferred Final Target date
* 2022-10-18: Fedora 37 Preferred Final Target date
* [2022-10-26]: Fedora 37 Final Target date #1
* 2022-10-25: Fedora 37 Final Target date #1




(From [https://www.python.org/dev/peps/pep-0664/#id4 Python 3.11 Release Schedule] and [https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html Fedora 37 Release Schedule] (dates in [] are based on Fedora 35 Release Schedule and will be adjusted accordingly when schedule for Fedora 37 is available).)
(From [https://www.python.org/dev/peps/pep-0664/#id4 Python 3.11 Release Schedule] and [https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html Fedora 37 Release Schedule].)


The schedule might appear somewhat tight for Fedora 37, but Python's [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/AKA3USBKFYKUQDSGDK4FNDYYWMKM7XKX/ annual release cycle was adapted for Fedora] and this worked fine since Python 3.9 and Fedora 33. It is now common that Python is upgraded on a similar schedule in every odd-numbered Fedora release.
The schedule might appear somewhat tight for Fedora 37, but Python's [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/AKA3USBKFYKUQDSGDK4FNDYYWMKM7XKX/ annual release cycle was adapted for Fedora] and this worked fine since Python 3.9 and Fedora 33. It is now common that Python is upgraded on a similar schedule in every odd-numbered Fedora release.
Line 129: Line 129:
<!-- 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?-->


* [TODO: releng ticket] Release engineering: [https://pagure.io/releng/issue/9810 #9810] <!-- 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/10321 #10321] <!-- 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.
<!-- 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 207: Line 207:
[https://www.python.org/dev/peps/pep-0664/ Python 3.11 Release Schedule]
[https://www.python.org/dev/peps/pep-0664/ Python 3.11 Release Schedule]


[https://www.python.org/dev/peps/pep-0664/#id7 Features for 3.11]
[https://www.python.org/dev/peps/pep-0664/#features-for-3-11 Features for 3.11]


[https://docs.python.org/3.11/whatsnew/3.11.html What's new in 3.11]
[https://docs.python.org/3.11/whatsnew/3.11.html What's new in 3.11]


[https://docs.python.org/3.11/whatsnew/3.11.html#id2 Porting to Python 3.11]
[https://docs.python.org/3.11/whatsnew/3.11.html#porting-to-python-3-11 Porting to Python 3.11]


== Release Notes ==
== Release Notes ==

Latest revision as of 13:59, 7 July 2022


Python 3.11

Summary

Update the Python stack in Fedora from Python 3.10 to Python 3.11, the newest major release of the Python programming language.

Owner


Current status

Detailed Description

We would like to upgrade Python to 3.11 in Fedora 37 thus we are proposing this plan early.

See the upstream notes at Features for 3.11 and What's new in 3.11.

Important dates and plan

  • 2021-05-03: Python 3.11 development begins
  • 2021-10-04: Python 3.11.0 alpha 1
    • Package it as python3.11 for testing purposes
    • Start the bootstrap procedure in Copr
    • Do a mass rebuild against every future release in Copr
  • 2021-11-02: Python 3.11.0 alpha 2
  • 2021-12-06: Python 3.11.0 alpha 3
  • 2022-01-03: Python 3.11.0 alpha 4
  • 2022-02-02: Python 3.11.0 alpha 5
  • 2022-02-08: Branch Fedora 36, Rawhide becomes future Fedora 37
    • The earliest point when we can start rebuilding in Koji side-tag
  • 2022-02-28: Python 3.11.0 alpha 6
  • 2022-04-05: Python 3.11.0 alpha 7
  • 2022-05-06: Python 3.11.0 beta 1
    • No new features beyond this point
  • 2022-05-30: Python 3.11.0 beta 2
    • The ideal point when we can start rebuilding in Koji
  • 2022-06-06: Expected side tag-merge (optimistic)
  • 2022-06-16: Python 3.11.0 beta 3
  • 2022-06-24: Expected side tag-merge (realistic)
  • 2022-07-09: Python 3.11.0 beta 4
  • 2022-07-18: Expected side tag-merge (pessimistic)
  • 2022-07-20: Fedora 37 Mass Rebuild
    • The mass rebuild happens with the fourth 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 38.
  • 2022-08-01: Python 3.11.0 candidate 1
    • This serves as "final" for our purposes.
  • 2022-08-09: Branch Fedora 37, Rawhide becomes future Fedora 38
  • 2022-08-09: Fedora 37 Change Checkpoint: Completion deadline (testable)
  • 2022-08-23: Fedora Beta Freeze
    • If rebuild with 3.11.0rc1 is needed, we should strive to do it before the freeze - there is a window of 3 weeks.
  • 2022-09-05: Python 3.11.0 candidate 2
  • 2022-09-13: Fedora 37 Beta Release (Preferred Target)
    • Beta will likely be released with 3.11.0rc2.
  • 2022-09-20: Fedora 37 Beta Target date #1
  • 2022-10-03: Python 3.11.0 final
  • 2022-10-04: Fedora 37 Final Freeze
    • We'll update to 3.11.0 final using a freeze exception.
  • 2022-10-18: Fedora 37 Preferred Final Target date
  • 2022-10-25: Fedora 37 Final Target date #1


(From Python 3.11 Release Schedule and Fedora 37 Release Schedule.)

The schedule might appear somewhat tight for Fedora 37, but Python's annual release cycle was adapted for Fedora and this worked fine since Python 3.9 and Fedora 33. It is now common that Python is 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.11.

There's also a benefit to the larger Python ecosystem: by building Fedora's packages against 3.11 while it's still in development, we can catch critical bugs before the final 3.11.0 release.

Scope

We will coordinate the work in a side tag and merge when ready.

  • Proposal owners:
    1. Introduce python3.11 for all Fedoras
    2. Prepare stuff in Copr as explained in description.
    3. Update python-rpm-macros so python3.11 builds python3
    4. Build python3.11 as the main Python
    5. Mass rebuild all the packages that runtime require python(abi) = 3.10 and/or libpython3.10.so.1.0 (~3800 known packages in October 2021)
    6. Build python3.11 as a non-main Python
  • 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.11. The python-maint team will be available to help with fixing issues.
  • Release engineering: #10321 A targeted rebuild for all python packages will be required, before the mass rebuild.
  • 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.10 is forward compatible with Python 3.11.

How To Test

Interested testers do not need special hardware. If you have a favourite Python 3 script, module, or application, please test it with Python 3.11 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.11 even before this change is implemented, in Fedora 34, 35 or 36.

In case your application requires other modules, or if you are testing an rpm package, it is necessary to install the 3.11 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.11. See https://copr.fedorainfracloud.org/coprs/g/python/python3.11/ for detailed instructions on how to enable Python 3.11 copr for mock.

Once the change is in place, test if your favourite 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 behaviour other than the Python 3 interpreter will be in version 3.11.

Dependencies

4000+ packages depend on Python 3 and ~3800 packages need rebuilding when Python is upgraded. 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.10 version (never needed before)
  • Contingency deadline: TBD
  • Blocks release? Yes, we'd like to block Fedora 37 release on at least 3.11.0rc1
  • Blocks product? See above

Documentation

Python 3.11 Release Schedule

Features for 3.11

What's new in 3.11

Porting to Python 3.11

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Python3.11&oldid=649343"