In order to get a PEP number, you need more than just an abstract.
You need a rough draft.
This commit is contained in:
parent
b48d675efd
commit
21d59a4d3b
|
@ -50,11 +50,11 @@ PEP Workflow
|
|||
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
|
||||
|
|
Loading…
Reference in New Issue