From Fedora Project Wiki
 
(23 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
<!-- 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 -->


Line 27: 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 34: Line 30:


<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
[[Category:SystemWideChange]]
<!-- [[Category:SystemWideChange]] -->
<!-- [[Category:SystemWideChange]] -->


Line 45: 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 67: 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 73: 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 80: 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 110: Line 106:
There are notes from the previous upgrade available, so this upgrade may go smoother: [[SIGs/Python/UpgradingPython]]
There are notes from the previous upgrade available, so this upgrade may go smoother: [[SIGs/Python/UpgradingPython]]


== Feedback ==
== Benefit to Fedora ==
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
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.
<!-- 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?-->


== Benefit to Fedora ==
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.
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
 
      Be sure to include the following areas if relevant:
      If this is a major capability update, what has changed?
          For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
      If this is a new functionality, what capabilities does it bring?
          For example: This change allows package upgrades to be performed automatically and rolled-back at will.
      Does this improve some specific package or set of packages?
          For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
      Does this improve specific Spins or Editions?
          For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
      Does this make the distribution more efficient?
          For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
      Is this an improvement to maintainer processes?
          For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
      Is this an improvement targeted as specific contributors?
          For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.  


    When a Change has multiple benefits, it's better to list them all.
== Scope ==


    Consider these Change pages from previous editions as inspiration:
We will coordinate the work in a side tag and merge when ready.
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
    https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
    https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
    https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
    https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->


== Scope ==
* 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|python3.11}} for all Fedoras
*# Prepare stuff in Copr as explained in description.
*# Update {{package|python-rpm-macros}} so {{package|python3.11}} builds {{package|python3}}
*# Build {{package|python3.11}} as the main Python
*# 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)
*# Build {{package|python3.11}} as a non-main Python


* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* 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.11/whatsnew/3.11.html#porting-to-python-3-11 Porting to Python 3.11]. 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/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* 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 -->
 
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: nope <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->


* Trademark approval: N/A (not needed for this Change)
* Policies and guidelines: nope <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->


* Alignment with Objectives:  
* Trademark approval: nope
<!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider -->
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
Line 166: Line 145:


<!-- 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.10 is forward compatible with Python 3.11.


== How To Test ==
== How To Test ==
Line 185: Line 164:
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


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 {{package|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 ==
== User Experience ==
Line 197: Line 181:
  - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
  - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->
-->
Regular distro users shouldn't notice any change in system behaviour other than the Python 3 interpreter will be in version 3.11.


== Dependencies ==
== Dependencies ==
Line 203: Line 189:
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


4000+ packages depend on Python 3 and ~3800 packages need rebuilding when Python is upgraded. 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: (What to do?  Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* 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) <!-- 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: N/A (not a System Wide Change) <!-- 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? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release? Yes, we'd like to block Fedora 37 release on at least 3.11.0rc1 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* Blocks product? See above <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==
Line 218: Line 205:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
[https://www.python.org/dev/peps/pep-0664/ Python 3.11 Release Schedule]
 
[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#porting-to-python-3-11 Porting to Python 3.11]


== Release Notes ==
== Release Notes ==
Line 226: Line 219:
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.  
-->
-->
* Migrating user installed packages - https://pagure.io/fedora-docs/release-notes/issue/503

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 Package-x-generic-16.pngpython3.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 Package-x-generic-16.pngpython3.11 for all Fedoras
    2. Prepare stuff in Copr as explained in description.
    3. Update Package-x-generic-16.pngpython-rpm-macros so Package-x-generic-16.pngpython3.11 builds Package-x-generic-16.pngpython3
    4. Build Package-x-generic-16.pngpython3.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 Package-x-generic-16.pngpython3.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 Package-x-generic-16.pngpython3.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"