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

Barry Warsaw bwarsaw@users.sourceforge.net
Mon, 01 Apr 2002 19:20:09 -0800


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

Modified Files:
	pep-0001.txt 
Log Message:
Add a note about how PEPs should really be more focussed, and contain
a single core idea.


Index: pep-0001.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0001.txt,v
retrieving revision 1.29
retrieving revision 1.30
diff -C2 -d -r1.29 -r1.30
*** pep-0001.txt	1 Mar 2002 00:42:48 -0000	1.29
--- pep-0001.txt	2 Apr 2002 03:20:07 -0000	1.30
***************
*** 44,51 ****
      for each PEP and changes its status.
  
!     The PEP process begins with a new idea for Python.  Each PEP must
!     have a champion -- someone who writes the PEP using the style and
!     format described below, shepherds the discussions in the
!     appropriate forums, and attempts to build community consensus
      around the idea.  The PEP champion (a.k.a. Author) should first
      attempt to ascertain whether the idea is PEP-able.  Small
--- 44,57 ----
      for each PEP and changes its status.
  
!     The PEP process begins with a new idea for Python.  It is highly
!     recommended that a single PEP contain a single key proposal or new
!     idea.  The more focussed the PEP, the more successfully it tends
!     to be.  The PEP editor reserves the right to reject PEP proposals
!     if they appear to unfocussed or too broad.  If in doubt, split
!     your PEP into several well-focussed ones.
! 
!     Each PEP must have a champion -- someone who writes the PEP using
!     the style and format described below, shepherds the discussions in
!     the appropriate forums, and attempts to build community consensus
      around the idea.  The PEP champion (a.k.a. Author) should first
      attempt to ascertain whether the idea is PEP-able.  Small