-
-
Notifications
You must be signed in to change notification settings - Fork 31k
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
gh-101015: Fix typing.get_type_hints
with unpacked *tuple
(PEP 646)
#101031
Conversation
8e11117
to
b28ee58
Compare
b28ee58
to
3bb3975
Compare
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.
This looks great @sobolevn -- thank you! I don't think it's any more hacky than the current code ;)
Just a small nit with the NEWS entry:
Misc/NEWS.d/next/Library/2023-01-14-12-58-21.gh-issue-101015.stWFid.rst
Outdated
Show resolved
Hide resolved
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.
The Windows test failure is unrelated
typing.ForwardRef
with *tuple
unpacktyping.get_type_hints
with unpacked *tuple
(PEP 646)
Thanks @sobolevn for the PR, and @AlexWaygood for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
GH-101254 is a backport of this pull request to the 3.11 branch. |
…PEP 646) (pythonGH-101031) (cherry picked from commit 807d6b5) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
Couple of thoughts:
ForwardRef
has way too many flagstyping.py
fix 😆), better ideas are welcome*tuple[int, int]
is improperly evaluated byget_type_hints
#101015