Add section on PEP Development Process, with github links.
This commit is contained in:
parent
908c2eb563
commit
2d90c47e44
21
pep-0484.txt
21
pep-0484.txt
|
@ -884,6 +884,18 @@ the notion that “explicit is better than implicit”, type hints are
|
|||
indeed *Pythonic*.
|
||||
|
||||
|
||||
PEP Development Process
|
||||
=======================
|
||||
|
||||
A live draft for this PEP lives on GitHub [github]_. There is also an
|
||||
issue tracker [issues]_, where much of the technical discussion takes
|
||||
place.
|
||||
|
||||
The draft on GitHub is updated regularly in small increments. The
|
||||
official PEPS repo [peps_] is (usually) only updated when a new draft
|
||||
is posted to python-dev.
|
||||
|
||||
|
||||
Acknowledgements
|
||||
================
|
||||
|
||||
|
@ -916,6 +928,15 @@ References
|
|||
.. [roberge]
|
||||
http://aroberge.blogspot.com/2015/01/type-hinting-in-python-focus-on.html
|
||||
|
||||
.. [github]
|
||||
https://github.com/ambv/typehinting
|
||||
|
||||
.. [issues]
|
||||
https://github.com/ambv/typehinting/issues
|
||||
|
||||
.. [peps]
|
||||
https://hg.python.org/peps/file/tip/pep-0484.txt
|
||||
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
|
Loading…
Reference in New Issue