Łukasz Langa <luk...@langa.pl> added the comment: > It may be deprecated but the usage still exists. This is a glossary, not a > manifesto.
Agreed. However, based on the current wording users will argue that Python documentation itself is stressing the lack of an intended purpose for annotations, equaling the typing use case with all other use cases (including future ones). This isn't our intent. I think it would be clearer to change the current wording from: > A metadata value associated with a variable, a class attribute or a > function or method parameter or return value, that has no specific > purpouse (i.e. it's up to the user to use it as they see fit). > (...) > Annotations can be used to specify :term:`type hints <type hint>`. to: > A metadata value associated with a variable, a class attribute or a > function or method parameter or return value, that stores a > :term:`type hint`. > (...) > Annotations can be used for other purposes unrelated to typing. This > usage is deprecated, see :pep:`563` for details. The `type hint` phrasing is already there, we just need to delete the word "global" that currently appears before "variable". Note that saying that annotations in class attributes and variables have no assigned meaning contradicts PEP 526. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32769> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
