This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients BTaskaya, docs@python, gvanrossum, levkivskyi, pablogsal
Date 2019-11-16.17:48:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1573926492.82.0.247834207809.issue37083@roundup.psfhosted.org>
In-reply-to
Content
Honestly I don't think that the exact places where TYPE_COMMENT goes in the grammar should be documented as part of the language reference.  For almost all of them we should be using type annotation syntax, and IMO for the remaining ones we should either add syntax or just move the declaration to a line by itself using `var: type` (PEP 526).

Also note that these are irrelevant to most users -- they only come into play when ast.parse(type_comments=True) is used, or when code is parsed by a separate tool like mypy.
History
Date User Action Args
2019-11-16 17:48:12gvanrossumsetrecipients: + gvanrossum, docs@python, levkivskyi, pablogsal, BTaskaya
2019-11-16 17:48:12gvanrossumsetmessageid: <1573926492.82.0.247834207809.issue37083@roundup.psfhosted.org>
2019-11-16 17:48:12gvanrossumlinkissue37083 messages
2019-11-16 17:48:12gvanrossumcreate