Repository navigation
fix: close release dependency and typing gaps - #305
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.
Follow up #304 with the remaining release-readiness fixes.
Raise the optional Pydantic minimum to 2.11.0: Pydantic 2.10 cannot validate the supported Python 3.12 generic-case example. Add a Python 3.12 CI job that smoke-tests the built wheel without extras at the minimum core dependency, then runs the suite against the installed wheel with Pydantic 2.11.0 and typing-extensions 4.12.2 outside the checkout.
Give collection factories their own type parameters so calls such as
Block.of("new", "featured")infer their element types instead ofUnknown. Cover the affected Block, TypedArray, Map, and Seq factories with positive and negative typing contracts, while preserving Seq subclass construction.Correct the remaining guide and tutorial examples and include them in strict Pyright checking. Run each document's assertions in a separate process through
just testand CI, including notebook cells with top-levelawait.Verification commands:
just lint,just test,just build, and the minimum-dependency installed-wheel commands in.github/workflows/python-package.yml.