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

Add a Last-Modified: header. 

Add a short description of the format for both the Author: and
Post-History: headers.

Elaborate a bit about how and where PEP discussions should be held.
This commit is contained in:
Barry Warsaw 2001-08-14 22:04:52 +00:00
parent c1d87738ff
commit 85c2313552
1 changed files with 19 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
pep-0001.txt
View File

@ -1,6 +1,7 @@
PEP: 1 PEP: 1
Title: PEP Purpose and Guidelines Title: PEP Purpose and Guidelines
Version: $Revision$ Version: $Revision$
Last-Modified: $Date$
Author: barry@zope.com (Barry A. Warsaw), Author: barry@zope.com (Barry A. Warsaw),
jeremy@zope.com (Jeremy Hylton) jeremy@zope.com (Jeremy Hylton)
Status: Active Status: Active
@ -85,9 +86,11 @@ PEP Work Flow
discussed on python-list@python.org and/or python-dev@python.org discussed on python-list@python.org and/or python-dev@python.org
will not be accepted. However, wherever possible, long open-ended will not be accepted. However, wherever possible, long open-ended
discussions on public mailing lists should be avoided. A better discussions on public mailing lists should be avoided. A better
strategy is to encourage public feedback directly to the PEP strategy is to encourage public feedback be sent directly to the
author, who collects and integrates the comments back into the PEP author during the early draft phases, who collects and
PEP. integrates the comments back into the PEP. Before code is
committed to CVS in a non-experimental way though, discussion must
be moved back to the python-dev and/or python-list mailing lists.
Once the authors have completed a PEP, they must inform the PEP Once the authors have completed a PEP, they must inform the PEP
editor that it is ready for review. PEPs are reviewed by the BDFL editor that it is ready for review. PEPs are reviewed by the BDFL
@ -192,6 +195,15 @@ PEP Style
* Replaces: <pep number> * Replaces: <pep number>
* Replaced-By: <pep number> * Replaced-By: <pep number>
The Author: header lists the email addresses and names of all the
authors/owners of the PEP. The format of the author entry should
be
address@dom.ain (Random J. User)
and if there are multiple authors, each should be on a separate
line following RFC 822 continuation line conventions.
Standards track PEPs must have a Python-Version: header which Standards track PEPs must have a Python-Version: header which
indicates the version of Python that the feature will be released indicates the version of Python that the feature will be released
with. Informational PEPs do not need a Python-Version: header. with. Informational PEPs do not need a Python-Version: header.
@ -203,6 +215,10 @@ PEP Style
the author, or on the python-list or python-dev email mailing the author, or on the python-list or python-dev email mailing
lists. lists.
Post-History: is used to record the dates of when new versions of
the PEP are posted to python-list and/or python-dev. The should
be in dd-mmm-yyyy format, e.g. 14-Aug-2001.
PEPs may have a Requires: header, indicating the PEP numbers that PEPs may have a Requires: header, indicating the PEP numbers that
this PEP depends on. this PEP depends on.