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

spelling

This commit is contained in:
David Goodger 2007-05-01 15:37:43 +00:00
parent 7dcc069cd6
commit b08fe48dbf
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0001.txt
View File

@ -63,7 +63,7 @@ PEP Work Flow
The PEP editors assign PEP numbers and change their status. The
current PEP editors are David Goodger and Barry Warsaw. Please send
all PEP-related email to <peps@python.org> (no cross-posting please).
Also see `PEP Editor Reponsibilities & Workflow`_ below.
Also see `PEP Editor Responsibilities & Workflow`_ below.
The PEP process begins with a new idea for Python. It is highly
recommended that a single PEP contain a single key proposal or new
@ -376,8 +376,8 @@ email in a timely manner, the PEP editor will make a unilateral
decision (it's not like such decisions can't be reversed :).
PEP Editor Reponsibilities & Workflow
=====================================
PEP Editor Responsibilities & Workflow
======================================
A PEP editor must subscribe to the <peps@python.org> list. All
PEP-related correspondence should be sent (or CC'd) to
@ -432,7 +432,7 @@ to the Python codebase. The PEP editors monitor the python-checkins
list for PEP changes, and correct any structure, grammar, spelling, or
markup mistakes we see.
The editors don't pass judgment on PEPs. We merely do the
The editors don't pass judgement on PEPs. We merely do the
administrative & editorial part. Except for times like this, there's
relatively low volume.