[Python-checkins] CVS: python/nondist/peps pep-0228.txt,1.1,1.2

Moshe Zadka python-dev@python.org
Sun, 5 Nov 2000 12:36:11 -0800


Update of /cvsroot/python/python/nondist/peps
In directory slayer.i.sourceforge.net:/tmp/cvs-serv9952

Modified Files:
	pep-0228.txt 
Log Message:
Added some issues because of Py-Dev feedback


Index: pep-0228.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0228.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -r1.1 -r1.2
*** pep-0228.txt	2000/11/05 16:55:24	1.1
--- pep-0228.txt	2000/11/05 20:36:06	1.2
***************
*** 1,3 ****
! PEP: Unassigned
  Title: Reworking Python's Numeric Model
  Version: $Revision$
--- 1,3 ----
! PEP: 228
  Title: Reworking Python's Numeric Model
  Version: $Revision$
***************
*** 76,104 ****
      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.
  
  Copyright
--- 76,90 ----
      mathematicl result.
  
  Numerical Python Issues
+ 
+     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