[Python-checkins] python/nondist/peps pep-0001.txt,1.40,1.41

[goodger@users.sourceforge.net]

Update of /cvsroot/python/python/nondist/peps
In directory sc8-pr-cvs1:/tmp/cvs-serv22160

Modified Files:
	pep-0001.txt 
Log Message:
add proactive review power for BDFL; add a description of acceptance criteria; and take some credit ;-)

Index: pep-0001.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0001.txt,v
retrieving revision 1.40
retrieving revision 1.41
diff -C2 -d -r1.40 -r1.41
*** pep-0001.txt	8 Nov 2002 04:48:16 -0000	1.40
--- pep-0001.txt	2 May 2003 21:34:44 -0000	1.41
***************
*** 3,7 ****
  Version: $Revision$
  Last-Modified: $Date$
! Author: Barry A. Warsaw, Jeremy Hylton
  Status: Active
  Type: Informational
--- 3,7 ----
  Version: $Revision$
  Last-Modified: $Date$
! Author: Barry A. Warsaw, Jeremy Hylton, David Goodger
  Status: Active
  Type: Informational
***************
*** 111,115 ****
      editor that it is ready for review.  PEPs are reviewed by the BDFL
      and his chosen consultants, who may accept or reject a PEP or send
!     it back to the author(s) for revision.
  
      Once a PEP has been accepted, the reference implementation must be
--- 111,130 ----
      editor that it is ready for review.  PEPs are reviewed by the BDFL
      and his chosen consultants, who may accept or reject a PEP or send
!     it back to the author(s) for revision.  For a PEP that is
!     pre-determined to be acceptable (e.g., it is an obvious win as-is
!     and/or its implementation has already been checked in) the BDFL
!     may also initiate a PEP review, first notifying the PEP author(s)
!     and giving them a chance to make revisions.
! 
!     For a PEP to be accepted it must meet certain minimum criteria.
!     It must be a clear and complete description of the proposed
!     enhancement.  The enhancement must represent a net improvement.
!     The proposed implementation, if applicable, must be solid and must
!     not complicate the interpreter unduly.  Finally, a proposed
!     enhancement must be "pythonic" in order to be accepted by the
!     BDFL.  (However, "pythonic" is an imprecise term; it may be
!     defined as whatever is acceptable to the BDFL.  This logic is
!     intentionally circular.)  See PEP 2 [10] for standard library
!     module acceptance criteria.
  
      Once a PEP has been accepted, the reference implementation must be
***************
*** 383,386 ****
--- 398,404 ----
  
      [9] http://docutils.sourceforge.net/
+ 
+     [10] PEP 2, Procedure for Adding New Modules, Faassen
+          http://www.python.org/peps/pep-0002.html