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

Revise guidelines for discussion of PEP before draft exists. The goal 

is to limit needless and uninformed discussion of an issue, not to
prevent all discussion.
This commit is contained in:
Jeremy Hylton 2000-10-16 20:32:29 +00:00
parent cddd347814
commit 5b4565c9b8
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

@ -61,10 +61,10 @@ PEP Workflow
Dictator for Life, Guido van Rossum <guido@beopen.com>) is the Dictator for Life, Guido van Rossum <guido@beopen.com>) is the
final arbitrator of the latter. final arbitrator of the latter.
Discussion concerning a PEP should initially be kept out of the In general, an initial draft of the PEP should be prepared before
python-dev and python-list mailing lists. Instead, comments discussion occurs on the python-dev and pyton-list mailing lists.
should be sent to, and collected by, the PEP owner, who has the The author should incorporate comments and feedback into this
responsibility to incorporate these comments into the document. initial draft when possible.
The authors of the PEP are then responsible for writing the PEP The authors of the PEP are then responsible for writing the PEP
and marshaling community support for it. The structure of a PEP and marshaling community support for it. The structure of a PEP