Repository navigation
feat!: require Python 3.12 and modernize type parameters - #304
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.
Raise the minimum Python version to 3.12 and migrate generic functions, methods, classes, and suitable aliases to modern type parameter syntax. Update package metadata, the lockfile, tooling, documentation, and CI to support Python 3.12–3.15. Python 3.11 users must remain on the previous major release.
Preserve explicit TypeVars where case covariance or type parameter defaults require them, and keep evaluated Option, Result, and TaggedUnion aliases for runtime introspection and Pydantic integration. Block and Map retain their legacy class declarations because early Python 3.12 dataclasses lose weak-reference support with a direct PEP 695 Generic base; their generic methods use modern syntax.
Add consumer typing and Pydantic coverage for modern generic declarations. Use named, typed functions in the getting-started pipeline and include the guide in Pyright checks so its examples remain type-correct.
Verification commands:
just lint,just test(Python 3.12–3.15),just build, andpython docs/guides/getting-started.py.