Python typing followup to #10048#10120
Merged
Merged
Conversation
leijurv
force-pushed
the
typing-followup
branch
from
90e5cee to
dd2e269
Compare
Co-authored-by: Saagar Jha <saagar@saagarjha.com> Co-authored-by: Claude <noreply@anthropic.com>
leijurv
force-pushed
the
typing-followup
branch
from
dd2e269 to
3852969
Compare
Contributor
|
Worth noting that I used |
peterbell10
approved these changes
Apr 29, 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
3 participants
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.
@jeffniu-openai said
PR plzhere: #10048 (comment)Making this PR on behalf of @saagarjha (he is waiting on #8913)
New contributor declaration
I am not making a trivial change, such as fixing a typo in a comment.
I have written a PR description following these
rules.
I have run
pre-commit run --from-ref origin/main --to-ref HEAD.Select one of the following.
Select one of the following.
littests.