-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
Improve typing.TypeGuard docstring #117521
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
Labels
Comments
JelleZijlstra
added a commit
to JelleZijlstra/cpython
that referenced
this issue
Apr 3, 2024
JelleZijlstra
added a commit
that referenced
this issue
Apr 4, 2024
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Apr 4, 2024
(cherry picked from commit b32789c) Co-authored-by: Jelle Zijlstra <[email protected]>
JelleZijlstra
added a commit
that referenced
this issue
Apr 4, 2024
…7538) (cherry picked from commit b32789c) Co-authored-by: Jelle Zijlstra <[email protected]>
Can this be closed, or must this be backported to 3.11? |
It can't be backported any further than it already has been, as Python 3.11 is no longer accepting any changes unless they relate to security issues. So this can be closed now, thanks! |
diegorusso
pushed a commit
to diegorusso/cpython
that referenced
this issue
Apr 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current docstring for
typing.TypeGuard
includes a single example, but that example does not useTypeGuard
, and in fact demonstrates behavior that differs from that ofTypeGuard
in essential ways. It would be less confusing if the TypeGuard example actually exemplified TypeGuard.Linked PRs
The text was updated successfully, but these errors were encountered: