F42 Change Proposal: Retire Python 3.8 (self-contained)

Retire python3.8

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.

Wiki
Announced

:link: Summary

The python3.8 package will be retired without replacement from Fedora Linux 42. Python 3.8 reached upstream End of Life 2024-10-07. RHEL 8 Python 3.8 Stream has been retired since May 2023. Debian Buster had Python 3.7, Bullseye has 3.9. Ubuntu 20.04 LTS (Focal Fossa) has Python 3.8, but standard support ends in April 2025. Fedora 42 release date is in April 2025 as well.

:link: Owner

:link: Detailed Description

The python3.8 package with the Python interpreter in version 3.8 was kept in Fedora only to make it possible for Fedora users to test their software against it. Python 3.8 is upstream EOL and is not shipped in RHEL anymore. Ubuntu LTS which has it also goes end of standard support by the time Fedora Linux 42 is expected to be released.

Hence, it will be retired. Users who still want to test against Python 3.8 can stay on Fedora Linux 41 or use any other older distribution.

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

:link: Feedback

This was discussed on the Python list prior to submitting the change proposal. There was almost no feedback, but the one reply I got was positive: Retire Python 3.8 from Fedora 42+? - python-devel - Fedora mailing-lists

:link: Benefit to Fedora

No energy will be spent on making an older Python buildable and safe. We will not ship unsupported and insecure software.

:link: Scope

  • Proposal owners: Retire python3.8 from rawhide just before Fedora 42 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 the Fedora Strategy: N/A (not needed for this Change)

:link: 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.

:link: Early Testing (Optional)

Do you require ‘QA Blueprint’ support? N

:link: How To Test

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

:link: User Experience

No more Python 3.8 to test user software on.

:link: Dependencies

None.

:link: 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

:link: Documentation

N/A (not a System Wide Change)

:link: Release Notes

Last edited by @amoloney 2024-12-12T16:15:09Z

Last edited by @amoloney 2024-12-12T16:15:09Z

2 Likes

How do you feel about the proposal as written?

  • Strongly in favor
  • In favor, with reservations
  • Neutral
  • Opposed, but could be convinced
  • Strongly opposed
0 voters

If you are in favor but have reservations, or are opposed but something could change your mind, please explain in a reply.

We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what you’d like to express, please simply give that post a :heart: instead of reiterating. You can even do this by email, by replying with the heart emoji or just “+1”. This will make long topics easier to follow.

Please note that this is an advisory “straw poll” meant to gauge sentiment. It isn’t a vote or a scientific survey. See About the Change Proposals category for more about the Change Process and moderation policy.

This change proposal has now been submitted to FESCo with ticket #3316 for voting.

To find out more, please visit our Changes Policy documentation.