iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Guido van Rossum 2017-12-04 08:46:27 -08:00 committed by GitHub
parent 9873d9fb19
commit e7fea64f2b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0484.txt
View File

@ -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
----------------