* Changed the "PEP Template" section to "PEP Formats and Templates",
in which plaintext and reStructuredText PEPs are described.
* Added "PEP Header Preamble" heading, for the RFC 2822 header
description.
- Rearranged some descriptions to match the header order.
- Removed the colons from header field names (e.g., "the Author
header").
- Added a description of the Content-Type header.
* Moved the plaintext-PEP-specific "PEP Formatting Requirements"
section to PEP 9. PEP 1 now deals only with content, not format.
* Minor edits, including:
- Capitalized "Standards Track" and "Informational" throughout.
- In "it's not like such decisions can be reversed", "can" should be
"can't"; fixed.
format of the Author: header to be "Random J. User <address@dom.ain>"
Update PEP 1 style guidelines.
Updated PEP 9 template.
Updated PEP 0 as an example.
to other PEP authors -- it is okay now to omit your email address from
this header, although we will be obscuring it soon).
Also, use peps@python.org as the PEP editor contact address instead of
Barry's personal address.
Remove Guido's email address.
Other updates explaining where address obscuring takes place and where
it doesn't.
Updated the Emacs file local variable section.
Add a short description of the format for both the Author: and
Post-History: headers.
Elaborate a bit about how and where PEP discussions should be held.
body of a PEP document. Also describe how to refer to PEP in the
References sections, including the use of www.python.org/peps as the
preferred link.
Added a section on reporting bugs and submitting patches w.r.t. PEPs.
track, and technical. The (new) latter type describes internal or
implementation changes that don't have a direct visible effect on the
Python language (e.g. Stackless).
David Goodger
Barry Warsaw
Andrew M. Kuchling
Fred Drake
Jeremy Hylton
unknown