[issue26982] Clarify forward annotations in PEP 484

Guido van Rossum added the comment: (And by "not" I meant "now". Sorry.) -- ___ Python tracker ___ ___

[issue26982] Clarify forward annotations in PEP 484

Guido van Rossum added the comment: The PEPs repo is not on github. Please resubmit this patch as a PR at https://github.com/python/peps. (Sorry for all the indirections to different trackers.) -- resolution: -> rejected status: open -> closed ___

[issue26982] Clarify forward annotations in PEP 484

Changes by Ivan Levkivskyi : -- nosy: +levkivskyi ___ Python tracker ___ ___

[issue26982] Clarify forward annotations in PEP 484

Changes by Guido van Rossum : -- assignee: docs@python -> gvanrossum nosy: +gvanrossum ___ Python tracker ___

[issue26982] Clarify forward annotations in PEP 484

Changes by James Tatum : Removed file: http://bugs.python.org/file42786/forward_references.patch ___ Python tracker ___

[issue26982] Clarify forward annotations in PEP 484

Changes by James Tatum : Added file: http://bugs.python.org/file42787/forward_references.patch ___ Python tracker ___

[issue26982] Clarify forward annotations in PEP 484

Changes by James Tatum : Added file: http://bugs.python.org/file42786/forward_references.patch ___ Python tracker ___

[issue26982] Clarify forward annotations in PEP 484

Changes by James Tatum : Removed file: http://bugs.python.org/file42785/forward_references.patch ___ Python tracker ___

[issue26982] Clarify forward annotations in PEP 484

New submission from James Tatum: In https://github.com/python/typeshed/issues/180, we discussed a slight ambiguity with PEP 484's mention of forward references. It wasn't entirely clear that they don't apply unless using function annotations. This patch attempts to clear up the ambiguity.