Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop Python 3.8 support #421

Merged
merged 2 commits into from
Oct 4, 2023

Conversation

whitequark
Copy link
Member

No description provided.

We dropped support for Python 3.7 some time ago, so these shims were
completely unused.
@whitequark whitequark force-pushed the drop-py38-support branch 2 times, most recently from 1bf3118 to 57ec890 Compare October 4, 2023 18:02
@whitequark whitequark added this pull request to the merge queue Oct 4, 2023
@whitequark whitequark removed this pull request from the merge queue due to a manual request Oct 4, 2023
Even Debian oldstable has Python 3.9 now.
@whitequark whitequark added this pull request to the merge queue Oct 4, 2023
Merged via the queue into GlasgowEmbedded:main with commit e4fd2dc Oct 4, 2023
9 of 10 checks passed
@whitequark whitequark deleted the drop-py38-support branch October 4, 2023 18:34
@ewenmcneill
Copy link

Noting for future reference: Ubuntu 20.04 LTS ("supported" until April 2025) has Python 3.8:

ewen@parthenon:~$ grep Ubuntu /etc/issue | cut -f 1 -d '\'
Ubuntu 20.04.6 LTS 
ewen@parthenon:~$ python3 --version
Python 3.8.10
ewen@parthenon:~$ 

(Having followed the glasgow chat thread I can understand the motiviation to proactively drop Python 3.8 support, especially given the complexity of supporting both 3.8 and 3.11/3.12. So I'm not suggesting any change. Just a heads up/search bait for what to be aware might be impacted. Also RHEL 8, and 7, have assorted older Python 3.x versions at least available, several of which are well out of even upstream Python support.)

Ewen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants