-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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-119180: Add discussion of annotations to the 3.14 What's New #124393
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.
Nice!
annotations. Annotations may be evaluated in the :attr:`~annotationlib.Format.VALUE` | ||
format (which evaluates annotations to runtime values, similar to the behavior in | ||
earlier Python versions), the :attr:`~annotationlib.Format.FORWARDREF` format | ||
(which replaces undefined names with special markers), and the | ||
:attr:`~annotationlib.Format.SOURCE` format (which returns annotations as strings). |
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.
These will render as VALUE
, FORWARDREF
, SOURCE
. Is that what we want, or would Format.VALUE
, Format.FORWARDREF
and Format.SOURCE
be better?
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 did intend these to render as VALUE
etc. Do you think adding Format
is better?
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 I'd weakly prefer Format.VALUE
, but it might make the markup quite verbose, and I don't have a strong opinion :-)
Co-authored-by: Alex Waygood <[email protected]>
(As I mentioned offline, my high-level feedback would be that it would be nice to have some more positive content about the motivations and advantages of this change. Overall the tone is a bit gloomy currently -- but it's overall a great change, that we have lots of reasons for! :-D ) |
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!
📚 Documentation preview 📚: https://cpython-previews--124393.org.readthedocs.build/