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

updated

This commit is contained in:
David Goodger 2004-07-16 19:27:23 +00:00
parent 9f10890b0b
commit 5591215fe0
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
pep-0001.txt
View File

@ -59,10 +59,12 @@ Each PEP must have a champion -- someone who writes the PEP using the
style and format described below, shepherds the discussions in the
appropriate forums, and attempts to build community consensus around
the idea. The PEP champion (a.k.a. Author) should first attempt to
ascertain whether the idea is PEP-able. Small enhancements or patches
often don't need a PEP and can be injected into the Python development
work flow with a patch submission to the SourceForge `patch manager`_
or `feature request tracker`_.
ascertain whether the idea is PEP-able. Posting to the
comp.lang.python newsgroup (a.k.a. python-list@python.org mailing
list) is recommended. Small enhancements or patches often don't need
a PEP and can be injected into the Python development work flow with a
patch submission to the SourceForge `patch manager`_ or `feature
request tracker`_.
The PEP champion then emails the PEP editor <peps@python.org> with a
proposed title and a rough, but fleshed out, draft of the PEP. This