-
-
Notifications
You must be signed in to change notification settings - Fork 32k
gh-118418: Use a default value for type_params
in typing._eval_type
#118431
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
Conversation
Do you have a prefence: should we add a NEWS entry? On one hand, this is a bugfix, on the other hand, |
I think we don't need to since we never released the (arguably) broken version. |
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.
Thanks! :-)
Thanks @sobolevn for the PR, and @AlexWaygood for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
…al_type` (pythonGH-118431) (cherry picked from commit 4a5ad84) Co-authored-by: Nikita Sobolev <[email protected]>
GH-118436 is a backport of this pull request to the 3.12 branch. |
…val_type` (GH-118431) (#118436) Co-authored-by: Nikita Sobolev <[email protected]>
This is a way for libs using undocumented and protected
_eval_type
not to fail with newly added function parameter.