-
-
Notifications
You must be signed in to change notification settings - Fork 32k
gh-105566: Deprecate unusual ways of creating typing.NamedTuple
classes
#105609
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
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.
Good cleanup!
return '<sentinel>' | ||
|
||
|
||
_sentinel = _Sentinel() |
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 think that = object()
is good enough for this case.
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 disagree. Using = object()
would mean that the displayed signature would be very ugly if somebody did help(typing.NamedTuple)
in the REPL
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.
Also, we'll be able to reuse the _Sentinel
class when we do #105570 :)
typing.NamedTuple
styping.NamedTuple
classes
Closes #105566
typing.NamedTuple
classes #105566📚 Documentation preview 📚: https://cpython-previews--105609.org.readthedocs.build/