Added some issues because of Py-Dev feedback

pep-0228.txt

@@ -1,4 +1,4 @@
-PEP: Unassigned
+PEP: 228
 Title: Reworking Python's Numeric Model
 Version: $Revision$
 Author: pep@zadka.site.co.il (Moshe Zadka)
@@ -75,31 +75,17 @@ Inexact Operations
     number. The functions in the "cmath" module will return the correct
     mathematicl result.
 
-    6. Rationale -- The rationale fleshes out the specification by
-       describing what motivated the design and why particular design
-       decisions were made.  It should describe alternate designs that
-       were considered and related work, e.g. how the feature is
-       supported in other languages.
-
-       The rationale should provide evidence of consensus within the
-       community and discuss important objections or concerns raised
-       during discussion.
-
-    7. Reference Implementation -- The reference implementation must
-       be completed before any PEP is given status 'final,' but it
-       need not be completed before the PEP is accepted.  It is better
-       to finish the specification and rationale first and reach
-       consensus on it before writing code.
-
-       The final implementation must include test code and
-       documentation appropriate for either the Python language
-       reference or the standard library reference.
-
 Numerical Python Issues
 
-       People using Numerical Python do that for high-performance
-       vector operations. Therefore, NumPy should keep it's hardware
-       based numeric model.
+    People using Numerical Python do that for high-performance
+    vector operations. Therefore, NumPy should keep it's hardware
+    based numeric model.
+
+Unresolved Issues
+
+    Which number literals will be exact, and which inexact?
+
+    How do we deal with IEEE 754?
 
 Copyright