[Python-checkins] CVS: python/nondist/peps pep-0236.txt,1.7,1.8

[Barry Warsaw]

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

Modified Files:
	pep-0236.txt 
Log Message:
Use new acceptable practices for PEP references.


Index: pep-0236.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0236.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -r1.7 -r1.8
*** pep-0236.txt	2001/06/05 16:42:27	1.7
--- pep-0236.txt	2001/07/05 19:08:50	1.8
***************
*** 19,26 ****
      contentious and disrupting.
  
!     The "Guidelines for Language Evolution" PEP [1] suggests ways to ease
      the pain, and this PEP introduces some machinery in support of that.
  
!     The "Statically Nested Scopes" PEP [2] is the first application, and
      will be used as an example here.
  
--- 19,26 ----
      contentious and disrupting.
  
!     PEP 5, Guidelines for Language Evolution[1] suggests ways to ease
      the pain, and this PEP introduces some machinery in support of that.
  
!     PEP 227, Statically Nested Scopes[2] is the first application, and
      will be used as an example here.
  
***************
*** 28,32 ****
  Intent
  
!     [Note:  This is policy, and so should eventually move into PEP 5[1]]
  
      When an incompatible change to core language syntax or semantics is
--- 28,32 ----
  Intent
  
!     [Note:  This is policy, and so should eventually move into PEP 5 [1]]
  
      When an incompatible change to core language syntax or semantics is
***************
*** 39,45 ****
         will be enforced.
  
!     3. The mechanisms described in the "Warning Framework" PEP [3] are used
!        to generate warnings, whenever possible, about constructs or
!        operations whose meaning may[4] change in release R.
  
      4. The new future_statement (see below) can be explicitly included in a
--- 39,45 ----
         will be enforced.
  
!     3. The mechanisms described in PEP 3, Warning Framework[3] are
!        used to generate warnings, whenever possible, about constructs
!        or operations whose meaning may[4] change in release R.
  
      4. The new future_statement (see below) can be explicitly included in a
***************
*** 281,285 ****
          machine?
  
!     A:  Outside the scope of this PEP, although PEP 5[1] suggests a grace
          period there too, and the future_statement may also have a role to
          play there.
--- 281,285 ----
          machine?
  
!     A:  Outside the scope of this PEP, although PEP 5 [1] suggests a grace
          period there too, and the future_statement may also have a role to
          play there.
***************
*** 338,346 ****
  References and Footnotes
  
!     [1] http://python.sourceforge.net/peps/pep-0005.html
  
!     [2] http://python.sourceforge.net/peps/pep-0227.html
  
!     [3] http://python.sourceforge.net/peps/pep-0230.html
  
      [4] Note that this is "may" and not "will":  better safe than sorry.  Of
--- 338,349 ----
  References and Footnotes
  
!     [1] PEP 5, Guidelines for Language Evolution, Prescod
!         http://www.python.org/peps/pep-0005.html
  
!     [2] PEP 227, Statically Nested Scopes, Hylton
!         http://www.python.org/peps/pep-0227.html
  
!     [3] PEP 230, Warning Framework, Van Rossum
!         http://www.python.org/peps/pep-0230.html
  
      [4] Note that this is "may" and not "will":  better safe than sorry.  Of