Informational PEPs can also have a status of Active.
This commit is contained in:
parent
cc385c1671
commit
6f15dc67f4
|
@ -109,6 +109,9 @@ PEP Workflow
|
||||||
v
|
v
|
||||||
Deferred
|
Deferred
|
||||||
|
|
||||||
|
Some informational PEPs may also have a status of `Active' if they
|
||||||
|
are never meant to be completed. E.g. PEP 1.
|
||||||
|
|
||||||
|
|
||||||
What belongs in a successful PEP?
|
What belongs in a successful PEP?
|
||||||
|
|
||||||
|
@ -165,7 +168,7 @@ PEP Style
|
||||||
Title: <pep title>
|
Title: <pep title>
|
||||||
Version: <cvs version string>
|
Version: <cvs version string>
|
||||||
Author: <list of authors' email and real name>
|
Author: <list of authors' email and real name>
|
||||||
Status: <Draft | Accepted | Deferred | Final>
|
Status: <Draft | Active | Accepted | Deferred | Final>
|
||||||
Type: <Informational | Standards Track>
|
Type: <Informational | Standards Track>
|
||||||
Created: <date created on, in dd-mmm-yyyy format>
|
Created: <date created on, in dd-mmm-yyyy format>
|
||||||
Post-History: <dates of postings to python-list and python-dev>
|
Post-History: <dates of postings to python-list and python-dev>
|
||||||
|
|
Loading…
Reference in New Issue