[Python-checkins] r54972 - peps/trunk/pep-3119.txt peps/trunk/pep-3141.txt

guido.van.rossum python-checkins at python.org
Wed Apr 25 23:05:32 CEST 2007


Author: guido.van.rossum
Date: Wed Apr 25 23:05:21 2007
New Revision: 54972

Modified:
   peps/trunk/pep-3119.txt
   peps/trunk/pep-3141.txt
Log:
Fix up references in PEP 3141.  Point PEP 3119 to PEP 3141.


Modified: peps/trunk/pep-3119.txt
==============================================================================
--- peps/trunk/pep-3119.txt	(original)
+++ peps/trunk/pep-3119.txt	Wed Apr 25 23:05:21 2007
@@ -547,10 +547,7 @@
 ABCs for Numbers
 ----------------
 
-**Open issues:** Define: ``Number``, ``Complex``, ``Real``,
-``Rational``, ``Integer``.  Maybe also ``Cardinal`` (``Integer`` >=
-0)?  We probably also need ``Index``, which converts to ``Integer``
-using ``__index__``.  This should be moved out to a separate PEP.
+ABCs for numerical types are defined in PEP 3141.
 
 
 Guidelines for Writing ABCs

Modified: peps/trunk/pep-3141.txt
==============================================================================
--- peps/trunk/pep-3141.txt	(original)
+++ peps/trunk/pep-3141.txt	Wed Apr 25 23:05:21 2007
@@ -13,9 +13,9 @@
 Abstract
 ========
 
-This proposal defines a hierarchy of Abstract Base Classes (ABCs)
-[#pep3119] to represent numbers and other algebraic entities similar
-to numbers.  It proposes:
+This proposal defines a hierarchy of Abstract Base Classes (ABCs) (see
+PEP 3119) to represent numbers and other algebraic entities similar to
+numbers.  It proposes:
 
 * A hierarchy of algebraic concepts, including monoids, groups, rings,
   and fields with successively more operators and constraints on their
@@ -49,7 +49,7 @@
 Although this PEP uses terminology from PEP 3119, the hierarchy is
 meaningful for any systematic method of defining sets of
 classes. **Todo:** link to the Interfaces PEP when it's ready. I'm
-also using the extra notation from [#pep3107] (annotations) to specify
+also using the extra notation from PEP 3107 (annotations) to specify
 some types.
 
 Object oriented systems have a general problem in constraining
@@ -443,16 +443,16 @@
 References
 ==========
 
-.. [#pep3119] Introducing Abstract Base Classes
+.. [1] Introducing Abstract Base Classes
    (http://www.python.org/dev/peps/pep-3119/)
 
-.. [#pep3107] Function Annotations
+.. [2] Function Annotations
    (http://www.python.org/dev/peps/pep-3107/)
 
 .. [3] Possible Python 3K Class Tree?, wiki page created by Bill Janssen
    (http://wiki.python.org/moin/AbstractBaseClasses)
 
-.. [#numericprelude] NumericPrelude: An experimental alternative
+.. [4] NumericPrelude: An experimental alternative
    hierarchy of numeric type classes
    (http://darcs.haskell.org/numericprelude/docs/html/index.html)
 
@@ -462,7 +462,7 @@
 
 Thanks to Neil Norwitz for helping me through the PEP process.
 
-The Haskell Numeric Prelude [#numericprelude] nicely condensed a lot
+The Haskell Numeric Prelude [4]_ nicely condensed a lot
 of experience with the Haskell numeric hierarchy into a form that was
 relatively easily adaptable to Python.
 


More information about the Python-checkins mailing list