[Python-checkins] CVS: python/nondist/peps pep-0001.txt,1.2,1.3

[Barry Warsaw]

Update of /cvsroot/python/python/nondist/peps
In directory slayer.i.sourceforge.net:/tmp/cvs-serv6428

Modified Files:
	pep-0001.txt 
Log Message:
PEP proposals must have a title and an abstract.


Index: pep-0001.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0001.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** pep-0001.txt	2000/07/25 17:59:08	1.2
--- pep-0001.txt	2000/08/07 23:00:47	1.3
***************
*** 49,61 ****
      and specifies a location (e.g. egroups, python.org, Roundup).
  
!     The champion then emails the PEP editor describing the proposal
!     and its title.  If the PEP editor approves, he will assign the PEP
!     a number, label it as standards track or informational, give it
!     status 'draft', and create and check-in an initial template for
!     the PEP.  The PEP editor will not unreasonably deny a PEP.
!     Reasons for denying PEP status include duplication of effort,
!     being technically unsound, or not in keeping with the Python
!     philosophy; the BDFL (Benevolent Dictator for Life, Guido van
!     Rossum <guido@beopen.com>) is the final arbitrator of the latter.
  
      Discussion concerning a PEP should initially be kept out of the
--- 49,63 ----
      and specifies a location (e.g. egroups, python.org, Roundup).
  
!     The champion then emails the PEP editor with a proposed title and
!     an abstract of about a paragraph in length.
! 
!     If the PEP editor approves, he will assign the PEP a number, label
!     it as standards track or informational, give it status 'draft',
!     and create and check-in an initial template for the PEP.  The PEP
!     editor will not unreasonably deny a PEP.  Reasons for denying PEP
!     status include duplication of effort, being technically unsound,
!     or not in keeping with the Python philosophy; the BDFL (Benevolent
!     Dictator for Life, Guido van Rossum <guido@beopen.com>) is the
!     final arbitrator of the latter.
  
      Discussion concerning a PEP should initially be kept out of the