A little bit of clarity and reorg.
This commit is contained in:
parent
bc75a3f95b
commit
0b34071cba
16
pep-0009.txt
16
pep-0009.txt
|
@ -24,12 +24,19 @@ Rationale
|
|||
your PEP submission won't get automatically rejected because of
|
||||
form.
|
||||
|
||||
To use this template you must first decide whether your PEP is
|
||||
going to be Informational or Standards Track. Most PEPs are
|
||||
Standards Track because they propose a new feature for the Python
|
||||
language or standard library. When in doubt, read PEP 1 for
|
||||
details.
|
||||
|
||||
Once you've decided which type of PEP yours is going to be, follow
|
||||
the directions in the appropriate section below.
|
||||
|
||||
|
||||
How to Use This Template for Standard Track PEPs
|
||||
|
||||
First, decide if your PEP is going to be Informational or
|
||||
Standards Track. Most PEPs are Standards Track; if yours is, then
|
||||
make a copy of this file and perform the following edits:
|
||||
- Make a copy of this file and perform the following edits.
|
||||
|
||||
- replace the "PEP: 9" header with "PEP: XXX" since you don't yet
|
||||
have a PEP number assignment.
|
||||
|
@ -107,8 +114,7 @@ How to Use This Template for Standard Track PEPs
|
|||
|
||||
How to Use This Template for Informational PEPs
|
||||
|
||||
If your PEP is an Information PEP, make a copy of this file and
|
||||
perform the following edits:
|
||||
- Make a copy of this file and perform the following edits.
|
||||
|
||||
- replace the "PEP: 9" header with "PEP: XXX" since you don't yet
|
||||
have a PEP number assignment.
|
||||
|
|
Loading…
Reference in New Issue