From Fedora Project Wiki
< Changes
Churchyard (talk | contribs) m (Syntax fix) |
Churchyard (talk | contribs) (Change Ready For Wrangler) |
||
| (12 intermediate revisions by the same user not shown) | |||
| Line 25: | Line 25: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeReadyForWrangler]] | ||
<!-- 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 86: | Line 86: | ||
== Feedback == | == Feedback == | ||
<!-- 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. --> | <!-- 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. --> | ||
See the [https://discussion.fedoraproject.org/t/f41-change-proposal-gimp-version-3-self-contained/120254/38 GIMP 3 discussion] for feedback from the GIMP maintainer. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 115: | Line 116: | ||
https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack) | https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack) | ||
--> | --> | ||
The Python maintainers will no longer regularly backport security fixes to Python 2.7 in RHEL, due to the the end of maintenance of RHEL 7 and the retirement of the Python 2.7 application stream in RHEL 8. We provided this obsolete package for 5 years beyond its retirement date and will continue to provide it until Fedora 40 goes end of life. Enough has been enough. | |||
We do not wish to simply orphan the package, as we are afraid it would not receive proper care if taken by somebody else. | |||
If there are potential maintainers interested in maintaining Python 2 in Fedora beyond Fedora 41, they can talk to us and demonstrate their ability and will to take care of Python 2 by joining the maintenance early. | |||
Users who need to run their application in Python 2 should do so on a platform that offers support for it. Running applications on unsupported Python is dangerous. | |||
Developers who still need to test their software on Python 2 can use containers with older Fedora releases or unsupported CentOS/RHEL versions. | |||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
** Coordinate closely with the GIMP maintainers. | |||
** `fedpkg retire python2.7` before the beta freeze if GIMP is ready. | |||
** Remove `Recommends: python2.7` from {{package|asv}} and {{package|tox}}. | |||
<!-- 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?--> | ||
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
** Retire or fix the remaining dependent packages. | |||
<!-- 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/ | * Release engineering: [https://pagure.io/releng/issue/12175 #12175] <!-- 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 --> | ||
* Policies and guidelines: | * Policies and guidelines: Using Python 2 is already forbidden for Fedora packages. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- 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. --> | <!-- 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: | * Trademark approval: not needed for this Change | ||
<!-- 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. --> | <!-- 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. --> | ||
* Alignment with the Fedora Strategy: | * Alignment with the Fedora Strategy: nope? | ||
<!-- Does your proposal align with the current Fedora Strategy: https://discussion.fedoraproject.org/t/fedora-strategy-2028-february-march-planning-work-and-roadmap-til-flock/43618 ? It's okay if it doesn't, but it's something to consider --> | <!-- Does your proposal align with the current Fedora Strategy: https://discussion.fedoraproject.org/t/fedora-strategy-2028-february-march-planning-work-and-roadmap-til-flock/43618 ? It's okay if it doesn't, but it's something to consider --> | ||
| Line 140: | Line 153: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Unless Python 2 stops being installable, we do not plan to Obsolete it. | |||
Users who upgrade to Fedora Linux 41+ from earlier releases with Python 2 installed, will likely still get it, but they will receive no support. | |||
== Early Testing (Optional) == | == Early Testing (Optional) == | ||
<!-- This is an optional step for system-wide changes to avail of. If you would like to build an initial proof of concept of your change and have a member of Fedora QA help you write and/or run some initial basic tests on your code, please email tests@fedoraproject.org and include the link to your change proposal. This step is *optional*. --> | <!-- This is an optional step for system-wide changes to avail of. If you would like to build an initial proof of concept of your change and have a member of Fedora QA help you write and/or run some initial basic tests on your code, please email tests@fedoraproject.org and include the link to your change proposal. This step is *optional*. --> | ||
Do you require 'QA Blueprint' support? | Do you require 'QA Blueprint' support? N <!-- Optional Step for System-Wide Changes only --> | ||
== How To Test == | == How To Test == | ||
| Line 162: | Line 177: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Try installing {{package|python2.7}} on Fedora Linux 41+. It should fail. | |||
== User Experience == | == User Experience == | ||
| Line 174: | Line 190: | ||
- 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. | ||
--> | --> | ||
Some users might be unhappy about this, but we decided to do it anyway. We cannot keep legacy software forever, Fedora Linux is not that kind of Linux. | |||
== Dependencies == | == Dependencies == | ||
| Line 179: | Line 196: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* [[Changes/Gimp_3]] | |||
== 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: | * Contingency mechanism: postpone to Fedora 42 <!-- 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: | * Contingency deadline: A week after Beta Freeze <!-- 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? | * Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== Documentation == | == Documentation == | ||
| Line 195: | Line 211: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
There is no more Python 2 in Fedora Linux 41+. | |||
== Release Notes == | == Release Notes == | ||
| Line 203: | 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. | ||
--> | --> | ||
There is no more Python 2 in Fedora Linux 41+. | |||
Latest revision as of 14:15, 24 June 2024
Retire Python 2.7
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.
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
The 
python2.7
Owner
- Name: Miro Hrončok
- Email: mhroncok@redhat.com
Current status
- Targeted release: Fedora Linux 41
- Last updated: 2024-06-24
- [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
The
- Fedora 41 is to be released in October 2024, nearly 5 years after the upstream EOL of Python 2.
- RHEL 7 will reach the end of its maintenance support 2 phase on 2024-06-30.
- CentOS Linux 7 will reach end of life (EOL) on 2024-06-30.
- RHEL 8 Python 2.7 application stream retirement date is June 2024.
Dependent packages
Based on repoquery --repo=rawhide{,-source} --whatrequires python2.7, the following packages still depend on
email2trac
GIMP
The rest of the dependents exist merely for GIMP.
GIMP will be updated to GIMP 3 with Python 3 support. Python 2 dependencies of GIMP will be retired.
If by the time of the Fedora 41 Beta Freeze (2024-08-20) no Release Candidate of GIMP 3 has come around, we will postpone the retirement of Python 2 to Fedora 42.
Feedback
See the GIMP 3 discussion for feedback from the GIMP maintainer.
Benefit to Fedora
The Python maintainers will no longer regularly backport security fixes to Python 2.7 in RHEL, due to the the end of maintenance of RHEL 7 and the retirement of the Python 2.7 application stream in RHEL 8. We provided this obsolete package for 5 years beyond its retirement date and will continue to provide it until Fedora 40 goes end of life. Enough has been enough.
We do not wish to simply orphan the package, as we are afraid it would not receive proper care if taken by somebody else. If there are potential maintainers interested in maintaining Python 2 in Fedora beyond Fedora 41, they can talk to us and demonstrate their ability and will to take care of Python 2 by joining the maintenance early.
Users who need to run their application in Python 2 should do so on a platform that offers support for it. Running applications on unsupported Python is dangerous.
Developers who still need to test their software on Python 2 can use containers with older Fedora releases or unsupported CentOS/RHEL versions.
Scope
- Proposal owners:
- Other developers:
- Retire or fix the remaining dependent packages.
- Release engineering: #12175
- Policies and guidelines: Using Python 2 is already forbidden for Fedora packages.
- Trademark approval: not needed for this Change
- Alignment with the Fedora Strategy: nope?
Upgrade/compatibility impact
Unless Python 2 stops being installable, we do not plan to Obsolete it. Users who upgrade to Fedora Linux 41+ from earlier releases with Python 2 installed, will likely still get it, but they will receive no support.
Early Testing (Optional)
Do you require 'QA Blueprint' support? N
How To Test
Try installing
User Experience
Some users might be unhappy about this, but we decided to do it anyway. We cannot keep legacy software forever, Fedora Linux is not that kind of Linux.
Dependencies
Contingency Plan
- Contingency mechanism: postpone to Fedora 42
- Contingency deadline: A week after Beta Freeze
- Blocks release? No
Documentation
There is no more Python 2 in Fedora Linux 41+.
Release Notes
There is no more Python 2 in Fedora Linux 41+.