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

Use number 9999 in a draft PEP (#234) 

Closes https://github.com/python/peps/issues/223
This commit is contained in:
Mariatta 2017-04-12 10:27:15 -07:00 committed by GitHub
parent 6f5d594ca2
commit 7b06cc339a
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pep-0001.txt
View File

@ -147,7 +147,7 @@ errors may be corrected by the editors).
The standard PEP workflow is:
* You, the PEP author, fork the `PEP repository`_, and create a file named
``pep-0xxx.rst`` that contains your new PEP. Use "XXX" as your draft PEP
``pep-9999.rst`` that contains your new PEP. Use "9999" as your draft PEP
number.
* Push this to your GitHub fork and submit a pull request.
* The PEP editors review your PR for structure, formatting, and other errors.

2
pep-0012.txt
View File

@ -58,7 +58,7 @@ directions below.
will allow PEPs to be rendered on GitHub. ``.txt`` extensions still
exists for legacy reasons.
- Replace the "PEP: 12" header with "PEP: XXX" since you don't yet
- Replace the "PEP: 12" header with "PEP: 9999" since you don't yet
have a PEP number assignment.
- Change the Title header to the title of your PEP.