Repository navigation
Remove Python 3.9 support - #1246
Merged
Merged
Conversation
Python 3.9 reached its end of life in October 2025, and GitHub's ubuntu-latest runners (Ubuntu 26.04) no longer provide it, which breaks every CI job pinned to 3.9. Remove support and testing of Python 3.9, and run the lint, optional-dependency, nooptionals and PyPy jobs on 3.10. Signed-off-by: Raphael Bizos <r.bizos@criteo.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Python 3.9 reached its end of life in October 2025, and
ubuntu-latestnowresolves to Ubuntu 26.04, where
actions/setup-pythonhas no Python 3.9, soevery job using 3.9 fails at setup. Same approach as #1075 for Python 3.8:
remove 3.9 from the classifiers,
requires-python, tox and CI, and run thejobs that used 3.9 (lint, optional dependencies, nooptionals, PyPy) on 3.10.
The remaining benchmark test error is unrelated and fixed by #1245.
@csmarchbanks