From Fedora Project Wiki
Line 94: Line 94:


== 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 110: Line 110:
<!-- 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 -->



Revision as of 11:27, 30 May 2022


Retire python3.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.

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

  • Targeted release: Fedora Linux 40
  • Last updated: 2022-05-30
  • 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 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 9 “Stretch” 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.

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

How To Test

User Experience

Dependencies

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