From Fedora Project Wiki
(Created page with " = Python 3.14 = {{Change_Proposal_Banner}} == Summary == Update the Python stack in Fedora from Python 3.13 to Python 3.14, the newest major release of the Python programming language. == Owner == <!-- For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. This should link to your home wiki page so we know who you are. --> * Name:...")
 
No edit summary
Line 118: Line 118:
* 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/dev/whatsnew/3.14.html#porting-to-python-3-14 Porting to Python 3.14]. The 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/dev/whatsnew/3.14.html#porting-to-python-3-14 Porting to Python 3.14]. The python-maint team will be available to help with fixing issues.


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/12397 #12397] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- 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 -->

Revision as of 11:35, 16 October 2024

Python 3.14

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

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

Owner


Current status

  • Targeted release: Fedora Linux 43
  • Last updated: 2024-10-16
  • [Announced]
  • [<will be assigned by the Wrangler> Discussion thread]
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

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

See the upstream notes at What's new in 3.14.

Important dates and plan

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

(From Python 3.14 Release Schedule and Fedora 43 Release Schedule.)

The schedule might appear somewhat tight for Fedora 43, 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.


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.14.

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

Scope

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

  • Proposal owners:
    1. Introduce python3.14 for all Fedoras
    2. Prepare stuff in Copr as explained in description.
    3. Update python-rpm-macros so python3.14 builds python3
    4. Build python3.14 as the main Python
    5. Mass rebuild all the packages that runtime require python(abi) = 3.13 and/or libpython3.13.so.1.0 (~4100 known packages in October 2024)
    6. Build python3.14 as a 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.14. The python-maint team will be available to help with fixing issues.
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with the Fedora Strategy:

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.13 is forward compatible with Python 3.14.

Early Testing (Optional)

Do you require 'QA Blueprint' support? N

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.14 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.14 even before this change is implemented, in Fedora 39, 40, 41 or 42.

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

Once the change is in place, test if your 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.14.

Dependencies

4500+ packages depend on Python 3 and ~4100 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.13 version (never needed before)
  • Contingency deadline: beta freeze
  • Blocks release? Yes, we'd like to block Fedora 43 release on at least 3.14.0rc1


Documentation

Python 3.14 Release Schedule

What's new in 3.14

Porting to Python 3.14

Release Notes

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