2001-06-26 13:57:11 -04:00
|
|
|
|
PEP: 260
|
|
|
|
|
|
Title: Simplify xrange()
|
|
|
|
|
|
Version: $Revision$
|
2006-03-23 15:13:19 -05:00
|
|
|
|
Last-Modified: $Date$
|
2001-06-26 13:57:11 -04:00
|
|
|
|
Author: guido@python.org (Guido van Rossum)
|
2001-08-14 15:16:31 -04:00
|
|
|
|
Status: Final
|
2001-06-26 13:57:11 -04:00
|
|
|
|
Type: Standards Track
|
|
|
|
|
|
Python-Version: 2.2
|
|
|
|
|
|
Created: 26-Jun-2001
|
|
|
|
|
|
Post-History: 26-Jun-2001
|
|
|
|
|
|
|
|
|
|
|
|
Abstract
|
|
|
|
|
|
|
|
|
|
|
|
This PEP proposes to strip the xrange() object from some rarely
|
|
|
|
|
|
used behavior like x[i:j] and x*n.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Problem
|
|
|
|
|
|
|
|
|
|
|
|
The xrange() function has one idiomatic use:
|
|
|
|
|
|
|
|
|
|
|
|
for i in xrange(...): ...
|
|
|
|
|
|
|
|
|
|
|
|
However, the xrange() object has a bunch of rarely used behaviors
|
|
|
|
|
|
that attempt to make it more sequence-like. These are so rarely
|
|
|
|
|
|
used that historically they have has serious bugs (e.g. off-by-one
|
|
|
|
|
|
errors) that went undetected for several releases.
|
|
|
|
|
|
|
|
|
|
|
|
I claim that it's better to drop these unused features. This will
|
|
|
|
|
|
simplify the implementation, testing, and documentation, and
|
|
|
|
|
|
reduce maintenance and code size.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Proposed Solution
|
|
|
|
|
|
|
|
|
|
|
|
I propose to strip the xrange() object to the bare minimum. The
|
|
|
|
|
|
only retained sequence behaviors are x[i], len(x), and repr(x).
|
|
|
|
|
|
In particular, these behaviors will be dropped:
|
|
|
|
|
|
|
|
|
|
|
|
x[i:j] (slicing)
|
|
|
|
|
|
x*n, n*x (sequence-repeat)
|
|
|
|
|
|
cmp(x1, x2) (comparisons)
|
|
|
|
|
|
i in x (containment test)
|
|
|
|
|
|
x.tolist() method
|
|
|
|
|
|
x.start, x.stop, x.step attributes
|
|
|
|
|
|
|
2001-07-05 10:50:56 -04:00
|
|
|
|
I also propose to change the signature of the PyRange_New() C API
|
|
|
|
|
|
to remove the 4th argument (the repetition count).
|
|
|
|
|
|
|
2001-06-26 13:57:11 -04:00
|
|
|
|
By implementing a custom iterator type, we could speed up the
|
|
|
|
|
|
common use, but this is optional (the default sequence iterator
|
|
|
|
|
|
does just fine).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Scope
|
|
|
|
|
|
|
2001-07-05 10:50:56 -04:00
|
|
|
|
This PEP affects the xrange() built-in function and the
|
|
|
|
|
|
PyRange_New() C API.
|
2001-06-26 13:57:11 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Risks
|
|
|
|
|
|
|
|
|
|
|
|
Somebody's code could be relying on the extended code, and this
|
|
|
|
|
|
code would break. However, given that historically bugs in the
|
|
|
|
|
|
extended code have gone undetected for so long, it's unlikely that
|
|
|
|
|
|
much code is affected.
|
|
|
|
|
|
|
|
|
|
|
|
|
2001-08-01 14:25:51 -04:00
|
|
|
|
Transition
|
|
|
|
|
|
|
|
|
|
|
|
For backwards compatibility, the existing functionality will still
|
|
|
|
|
|
be present in Python 2.2, but will trigger a warning. A year
|
|
|
|
|
|
after Python 2.2 final is released (probably in 2.4) the
|
|
|
|
|
|
functionality will be ripped out.
|
|
|
|
|
|
|
|
|
|
|
|
|
2001-06-26 13:57:11 -04:00
|
|
|
|
Copyright
|
|
|
|
|
|
|
|
|
|
|
|
This document has been placed in the public domain.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Local Variables:
|
|
|
|
|
|
mode: indented-text
|
|
|
|
|
|
indent-tabs-mode: nil
|
|
|
|
|
|
End:
|
