Nick Coghlan 2af18441e8 Further updates to PEP 1 to better reflect current practice ... - identify the current PEP editors and clarify their role - separate out PEP administrative email from design discussion - reference implementations typically co-evolve with their PEP - it's OK to get a PEP number before a PEP is ready for python-dev - eliminate most of the ambiguous 'we' references (Initial patch by Chris Jerdonek)		2012-12-22 21:30:14 +10:00
..
__init__.py	…
constants.py	Further updates to PEP 1 to better reflect current practice	2012-12-22 21:30:14 +10:00
output.py	Defer both PEPs about speeding up the release cycle	2012-10-20 00:28:15 +10:00
pep.py	…