-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Fix tuple[Any, ...] subtyping #16108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
hauntsaninja
merged 11 commits into
python:master
from
hauntsaninja:tuple-any-subtyping
Sep 14, 2023
Merged
Changes from 8 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
2044720
Fix tuple[Any, ...] subtyping
hauntsaninja 6a4df2b
error
hauntsaninja c2250f8
fix meet
hauntsaninja e64a6cd
Revert "fix meet"
hauntsaninja 17ad1ca
suggestion
hauntsaninja d5812b6
use mapped type
hauntsaninja 03fda8b
zip
hauntsaninja 9840c37
base
hauntsaninja 2c4f791
Revert "base"
hauntsaninja e99d2f0
check
hauntsaninja 5c03731
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you need the last commit? This condition is always true because of the surrounding
if(each tuple fallback hasbuiltins.tuplein MRO), and also now this check looks wrong because it may trigger in unrelated cases involving something likeclass M(Generic[T], tuple[int, ...]): ....What you had before was almost right, except you didn't need the check
len(mapped.args) == 1, it should be always true ifmapped.type.fullname == "builtins.tuple".Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I misinterpreted your comment here #16108 (comment)
Ugh, I tried to test theI can't actually find a test, even with various NamedTuplesclass M(Generic[T], tuple[int, ...]): ...case but I did it backwardsThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you will not be able to come up with a test case, don't try to hard. It may be not easy to trigger such edge case (because of how user defined tuple types are represented). You already have enough test cases :-)
(I would still remove the unneeded len check)