[Python-checkins] peps: In order to get a PEP number, you need more than just an abstract.

[georg.brandl]

http://hg.python.org/peps/rev/833b0865f6b2
changeset:   152:833b0865f6b2
user:        Barry Warsaw <barry at python.org>
date:        Wed Aug 23 15:58:05 2000 +0000
summary:
  In order to get a PEP number, you need more than just an abstract.
You need a rough draft.

files:
  pep-0001.txt |  4 ++--
  1 files changed, 2 insertions(+), 2 deletions(-)


diff --git a/pep-0001.txt b/pep-0001.txt
--- a/pep-0001.txt
+++ b/pep-0001.txt
@@ -50,11 +50,11 @@
     and specifies a location (e.g. egroups, python.org, Roundup).
 
     The champion then emails the PEP editor with a proposed title and
-    an abstract of about a paragraph in length.
+    a rough, but fleshed out, draft of the PEP.
 
     If the PEP editor approves, he will assign the PEP a number, label
     it as standards track or informational, give it status 'draft',
-    and create and check-in an initial template for the PEP.  The PEP
+    and create and check-in the initial draft of the PEP.  The PEP
     editor will not unreasonably deny a PEP.  Reasons for denying PEP
     status include duplication of effort, being technically unsound,
     or not in keeping with the Python philosophy; the BDFL (Benevolent

-- 
Repository URL: http://hg.python.org/peps