Back out sum() change.
This commit is contained in:
parent
3da1186cdd
commit
3f7d8a1f10
10
pep-3000.txt
10
pep-3000.txt
|
@ -15,9 +15,8 @@ Abstract
|
|||
========
|
||||
|
||||
This PEP describes the changes currently envisioned in Python 3.0
|
||||
(also called Python 3000), a
|
||||
hypothetical future release of Python that can break backwards
|
||||
compatibility with the existing body of Python code.
|
||||
(also called Python 3000), a hypothetical future release of Python that
|
||||
can break backwards compatibility with the existing body of Python code.
|
||||
|
||||
The list of features included in this document is subject to change
|
||||
and isn't binding on the Python development community; features may be
|
||||
|
@ -90,8 +89,6 @@ Built-ins
|
|||
* Introduce ``trunc()``, which would call the ``__trunc__()`` method on its
|
||||
argument; suggested use if for objects like float where calling ``__int__()``
|
||||
has data loss, but an integral representation is still desired [8]_
|
||||
* The second argument to ``sum()`` will returned if the first argument is
|
||||
empty, otherwise it is ignored [10]_
|
||||
|
||||
To be removed:
|
||||
|
||||
|
@ -151,9 +148,6 @@ References
|
|||
.. [9] Guido's blog ("The fate of reduce() in Python 3000")
|
||||
http://www.artima.com/weblogs/viewpost.jsp?thread=98196
|
||||
|
||||
.. [10] python-dev email ("Rationale for sum()'s design?")
|
||||
http://mail.python.org/pipermail/python-dev/2005-March/052183.html
|
||||
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
|
Loading…
Reference in New Issue