[Python-checkins] python/nondist/peps pep-0012.txt,1.1,1.2

[goodger@users.sourceforge.net]

Update of /cvsroot/python/python/nondist/peps
In directory usw-pr-cvs1:/tmp/cvs-serv32150

Modified Files:
	pep-0012.txt 
Log Message:
Tracked Barry's changes to PEP 9.

Index: pep-0012.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0012.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** pep-0012.txt	26 Aug 2002 16:31:58 -0000	1.1
--- pep-0012.txt	30 Aug 2002 03:15:51 -0000	1.2
***************
*** 21,29 ****
  
  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!**
  
! To get the text version of this file, look at the top of the page and
! click on the link titled "PEP Source".
  
  If you would prefer not to use markup in your PEP, please see PEP 9,
--- 21,29 ----
  
  Note: if you are reading this PEP via the web, you should first grab
! 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 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,
***************
*** 52,58 ****
  
  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
--- 52,59 ----
  
  To use this template you must first decide whether your PEP is going
! 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
***************
*** 73,78 ****
    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.
  
  - If there is a mailing list for discussion of your new feature, add a
--- 74,80 ----
    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 (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
***************
*** 120,124 ****
  
    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.
  
  - Add a Replaces header if your PEP obsoletes an earlier PEP.  The
--- 122,126 ----
  
    You must manually add new dates and check them in.  If you don't
!   have check-in privileges, send your changes to the PEP editors.
  
  - Add a Replaces header if your PEP obsoletes an earlier PEP.  The
***************
*** 144,149 ****
    formfeed character ("^L", or ``\f``).
  
! - Send your PEP submission to the PEP editor, Barry Warsaw, at
!   peps@python.org.
  
  
--- 146,150 ----
    formfeed character ("^L", or ``\f``).
  
! - Send your PEP submission to the PEP editors at peps@python.org.