From Fedora Project Wiki
(Name, summary, owner, targeted release)
(Add trackers)
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<!-- 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 -->


= Retire python3.5 =
= Retire python3.7 =
 
{{Change_Proposal_Banner}}


== Summary ==
== Summary ==
Line 24: Line 22:


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF40]]
<!-- 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 42: Line 40:
ON_QA -> change is fully code complete
ON_QA -> change is fully code complete
-->
-->
* FESCo issue: <will be assigned by the Wrangler>
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4ERGFGR4PRXR5HQMLD45HSGBOYZNXLSG/ devel thread]
* Tracker bug: <will be assigned by the Wrangler>
* FESCo issue: [https://pagure.io/fesco/issue/2816 #2816]
* Release notes tracker: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2105404 #2105404]
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/855 #855]


== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
The {{package|python3.7}} package with the Python interpreter in version 3.7 will be kept in Fedora after upstream EOL ([https://devguide.python.org/#status-of-python-branches 2023-06-27]) only to make it possible for Fedora users to test their software against the Python version shipped in Debian 10 “Buster” LTS.
[https://wiki.debian.org/LTS Debian 10 “Buster” LTS is End of Life in 2024-06]. This happens couple months after the planned release of Fedora 40. Hence, we decided to retire (completely remove) {{package|python3.7}} from Fedora 40, before it gets released. Users who target Debian 10 can use Fedora 39 until it EOLs.
Note that {{package|python3.6}} will remain available for the foreseeable future to support developers who target RHEL 8.


== 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. -->
This was discussed on the Python list prior to submitting the change proposal: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/W74WYEVGYAE57KVLCG73I75LZYKKUMXS/
There was no pushback.


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 80: Line 89:
     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)
-->
-->
There is no direct benefit here, except that we don't want to maintain it anymore and we don't think it's a good idea either.
Consider this change proposal a louder orphaning, except that we will continue to maintain the package in older released and supported Fedoras (38 and 39). If you wish to continue maintaining Python 3.7 in Fedora past Fedora Linux 40, please [[SIGs/Python|speak to us]] first.


== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners: Retire {{package|python3.7}} from rawhide just before Fedora 40 is branched . Obsolete it from  {{package|fedora-obsolete-packages}} if it causes troubles on upgrades. Make sure no Fedora package depends on it in any way (incl. weak dependencies).
<!-- 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: N/A (not needed for this Change)
<!-- 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: N/A (not needed for this Change)
<!-- 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 98: Line 111:
<!-- 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 Objectives:  
* Alignment with Objectives: N/A (not needed for this Change)
<!-- 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 -->
<!-- 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 -->


Line 105: Line 118:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
The package will no longer be available from the repositories, but it may remain on existing installations. If it causes troubles on upgrade, it needs to be obsoleted.


== How To Test ==
== How To Test ==
Line 123: Line 136:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
Install Fedora 40. Try to install Python 3.7 via dnf or similar means. It should not be found.


== User Experience ==
== User Experience ==
Line 136: Line 149:
  - 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.
-->
-->
No more Python 3.7 to test user software on.


== Dependencies ==
== Dependencies ==
Line 141: Line 155:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
None.


== Contingency Plan ==
== Contingency Plan ==

Latest revision as of 17:59, 8 July 2022


Retire python3.7

Summary

The python3.7 package will be retired without replacement from Fedora Linux 40. Python 3.7 will be End of Life in June 2023 and it will be kept around only to test software targeting Debian 10 “Buster” LTS. The removal is more or less aligned with Debian 10 TLS EOL (June 2024) -- Fedora 39 (the last one to include Python 3.7) will likely EOL on 2024-11-12.

Owner


Current status

Detailed Description

The python3.7 package with the Python interpreter in version 3.7 will be kept in Fedora after upstream EOL (2023-06-27) only to make it possible for Fedora users to test their software against the Python version shipped in Debian 10 “Buster” LTS.

Debian 10 “Buster” LTS is End of Life in 2024-06. This happens couple months after the planned release of Fedora 40. Hence, we decided to retire (completely remove) python3.7 from Fedora 40, before it gets released. Users who target Debian 10 can use Fedora 39 until it EOLs.

Note that python3.6 will remain available for the foreseeable future to support developers who target RHEL 8.

Feedback

This was discussed on the Python list prior to submitting the change proposal: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/W74WYEVGYAE57KVLCG73I75LZYKKUMXS/

There was no pushback.

Benefit to Fedora

There is no direct benefit here, except that we don't want to maintain it anymore and we don't think it's a good idea either.

Consider this change proposal a louder orphaning, except that we will continue to maintain the package in older released and supported Fedoras (38 and 39). If you wish to continue maintaining Python 3.7 in Fedora past Fedora Linux 40, please speak to us first.

Scope

  • Proposal owners: Retire python3.7 from rawhide just before Fedora 40 is branched . Obsolete it from fedora-obsolete-packages if it causes troubles on upgrades. Make sure no Fedora package depends on it in any way (incl. weak dependencies).
  • Other developers: N/A (not needed for this Change)
  • Release engineering: N/A (not needed for this Change)
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives: N/A (not needed for this Change)

Upgrade/compatibility impact

The package will no longer be available from the repositories, but it may remain on existing installations. If it causes troubles on upgrade, it needs to be obsoleted.

How To Test

Install Fedora 40. Try to install Python 3.7 via dnf or similar means. It should not be found.

User Experience

No more Python 3.7 to test user software on.

Dependencies

None.

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Documentation

N/A (not a System Wide Change)

Release Notes