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

Tracked Barry's changes to PEP 9.

This commit is contained in:
David Goodger 2002-08-30 03:15:51 +00:00
parent 4b0602458a
commit 8d2831d855
1 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
pep-0012.txt
View File

@ -20,11 +20,11 @@ in PEP 1 [1]_, this should make it easy for you to conform your own
PEPs to the format outlined below.
Note: if you are reading this PEP via the web, you should first grab
the text (reStructuredText) version in order to complete the steps
below. **DO NOT USE THE HTML FILE AS YOUR TEMPLATE!**
the text (reStructuredText) source of this PEP in order to complete
the steps below. **DO NOT USE THE HTML FILE AS YOUR TEMPLATE!**
To get the text version of this file, look at the top of the page and
click on the link titled "PEP Source".
To get the source of this (or any) PEP, look at the top of the HTML
page and click on the link titled "PEP Source".
If you would prefer not to use markup in your PEP, please see PEP 9,
"Sample Plaintext PEP Template" [2]_.
@ -51,9 +51,10 @@ How to Use This Template
========================
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.
to be an Informational or Standards Track PEP. 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
or contact the PEP editors <peps@python.org>.
Once you've decided which type of PEP yours is going to be, follow the
directions below.
@ -72,8 +73,9 @@ directions below.
- Change the Author header to include your name, and optionally your
email address. Be sure to follow the format carefully: your name
must appear first, and it must not be contained in parentheses.
Your email address may appear second (it can also be omitted) and if
it appears, it must appear in angle brackets.
Your email address may appear second (or it can be omitted) and if
it appears, it must appear in angle brackets. It is okay to
obfuscate your email address.
- If there is a mailing list for discussion of your new feature, add a
Discussions-To header right after the Author header. You should not
@ -119,7 +121,7 @@ directions below.
Post-History: 14-Aug-2001, 03-Sept-2001
You must manually add new dates and check them in. If you don't
have check-in privileges, send your changes to the PEP editor.
have check-in privileges, send your changes to the PEP editors.
- Add a Replaces header if your PEP obsoletes an earlier PEP. The
value of this header is the number of the PEP that your new PEP is
@ -143,8 +145,7 @@ directions below.
- Leave the Emacs stanza at the end of this file alone, including the
formfeed character ("^L", or ``\f``).
- Send your PEP submission to the PEP editor, Barry Warsaw, at
peps@python.org.
- Send your PEP submission to the PEP editors at peps@python.org.
ReStructuredText PEP Formatting Requirements