Message316648
| Author | gvanrossum |
|---|---|
| Recipients | adelfino, cheryl.sabella, docs@python, gvanrossum, levkivskyi, lukasz.langa, matrixise, r.david.murray |
| Date | 2018-05-15.12:20:58 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAP7+vJJJ=aJ=h3Q-EGJZB2XvkH5c7AZJGGSXJEw6yhvWniZDUg@mail.gmail.com> |
| In-reply-to | <1526386612.15.0.682650639539.issue32769@psf.upfronthosting.co.za> |
| Content | |
|---|---|
I actually intended to say that annotations continue to be usable for non-typing purposes (beyond ClassVar/InitVar). It may be deprecated but the usage still exists. This is a glossary, not a manifesto. I'm fine with adding that the main use of annotations is for type hints of course. And I was mostly reacting to the fact that the text that was just committed seemed to imply that 'annotation' refers to something stored at runtime in __annotations__ while 'type hint' was a syntactic form (and this is borne out by the omission of *local* type hints from the section on annotations). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-05-15 12:20:58 | gvanrossum | set | recipients: + gvanrossum, r.david.murray, docs@python, lukasz.langa, matrixise, levkivskyi, cheryl.sabella, adelfino |
| 2018-05-15 12:20:58 | gvanrossum | link | issue32769 messages |
| 2018-05-15 12:20:58 | gvanrossum | create | |