From e7fea64f2b4d9821b43d75e54576752095d69314 Mon Sep 17 00:00:00 2001 From: Guido van Rossum Date: Mon, 4 Dec 2017 08:46:27 -0800 Subject: [PATCH] Add links to PEP 563. (#451) Mention an updated schedule for non-provisional status and the end of non-typing annotations in PEP 563, and link there for the __future__ statement as well. --- pep-0484.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/pep-0484.txt b/pep-0484.txt index a3d76f88b..967363475 100644 --- a/pep-0484.txt +++ b/pep-0484.txt @@ -2253,6 +2253,11 @@ allowed use of annotations in Python 3.8. This should give authors of packages that use annotations plenty of time to devise another approach, even if type hints become an overnight success. +(*UPDATE:* As of fall 2017, the timeline for the end of provisional +status for this PEP and for the ``typing.py`` module has changed, and +so has the deprecation schedule for other uses of annotations. For +the updated schedule see PEP 563.) + Another possible outcome would be that type hints will eventually become the default meaning for annotations, but that there will always remain an option to disable them. For this purpose the current @@ -2333,6 +2338,9 @@ follows:: Such a ``__future__`` import statement may be proposed in a separate PEP. +(*UPDATE:* That ``__future__`` import statement and its consequences +are discussed in PEP 563.) + The double colon ----------------