Repository navigation
chore: pin local development to Python 3.12 to match CI - #998
Merged
Merged
Conversation
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.
Why
CI runs the unit, integration and E2E suites on Python 3.12, the minimum supported version, but
uv syncin a fresh checkout picks the newest installed interpreter. Local runs on a newer Python have missed 3.12-only failures: a runtime-evaluated annotation that only works from 3.13, and a version-specific argparse message. They also skip the native discovery path, which only activates on Python 3.12's Unicode version.Changes
.python-versionwith3.12, souv sync,uv runandmaketargets use the same interpreter as CI by default. Developers can still pick another version explicitly.Verification
uv sync --all-extrasin a fresh worktree creates a 3.12 environment.make check-ciandmake testpass on it.