Repository navigation
build: Drop support for Python 3.10 - #4029
Merged
Merged
Conversation
joelostblom
force-pushed
the
build/drop-py310
branch
from
June 3, 2026 12:56
01c075f to
b52ce4f
Compare
It hasn't received bug fixes for years and is soon out of security fixes as well.
joelostblom
force-pushed
the
build/drop-py310
branch
from
June 3, 2026 13:01
b52ce4f to
9ef4768
Compare
# Conflicts: # .github/workflows/build-free-threaded.yml # .github/workflows/weekly.yml # uv.lock
alec-bike
reviewed
Aug 15, 2026
alec-bike
reviewed
Aug 15, 2026
alec-bike
requested changes
Aug 15, 2026
alec-bike
left a comment
alec-bike
left a comment
Contributor
There was a problem hiding this comment.
Looks good. A couple of minor notes to consolidate some dangling "from typing import..." statements.
Contributor
Author
|
Thanks @alec-bike! I updated with your suggestions |
alec-bike
approved these changes
Aug 16, 2026
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.
3.10 hasn't received bug fixes for years and is soon out of security fixes as well.
There are two PRs with py3.10 specific workarounds that we could avoid: #4010 and #4027
We might even want to adopt a stricter policy like that for the general scientific python ecosystem, which dropped py 3.11 in the end of 2025.