-
-
Notifications
You must be signed in to change notification settings - Fork 32k
bpo-44353: Correct docstring for NewType
#29785
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
The docstring for `typing.NewType` is no longer strictly accurate, now that `NewType` is a class, rather than a function
NewType
NewType
@gvanrossum: Please replace |
Sorry to bother you @gvanrossum — could this possibly be backported to 3.10 as well? 🙂 |
Thanks @AlexWaygood for the PR, and @gvanrossum for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
Sorry @AlexWaygood and @gvanrossum, I had trouble checking out the |
Thanks @AlexWaygood for the PR, and @gvanrossum for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
The docstring for `typing.NewType` is no longer strictly accurate, now that `NewType` is a class, rather than a function (cherry picked from commit 93c65df) Co-authored-by: Alex Waygood <[email protected]>
GH-29796 is a backport of this pull request to the 3.10 branch. |
The docstring for `typing.NewType` is no longer strictly accurate, now that `NewType` is a class, rather than a function (cherry picked from commit 93c65df) Co-authored-by: Alex Waygood <[email protected]>
Thanks @Fidget-Spinner! |
The docstring for `typing.NewType` is no longer strictly accurate, now that `NewType` is a class, rather than a function
The docstring for
typing.NewType
is no longer strictly accurate, now thatNewType
is a class, rather than a functionhttps://bugs.python.org/issue44353