diff options
| author | Guido van Rossum <guido@python.org> | 2001-07-05 13:27:48 (GMT) |
|---|---|---|
| committer | Guido van Rossum <guido@python.org> | 2001-07-05 13:27:48 (GMT) |
| commit | 3f56166b1aff15136960dfc8ad90f571e14be01a (patch) | |
| tree | 6d39af58334274d80e96f5d59a6e1f3b12f91588 /Doc | |
| parent | 25ddc6330f1977c4c650f1002586faf4f7b2c639 (diff) | |
| download | cpython-3f56166b1aff15136960dfc8ad90f571e14be01a.zip cpython-3f56166b1aff15136960dfc8ad90f571e14be01a.tar.gz cpython-3f56166b1aff15136960dfc8ad90f571e14be01a.tar.bz2 | |
Rip out the fancy behaviors of xrange that nobody uses: repeat, slice,
contains, tolist(), and the start/stop/step attributes. This includes
removing the 4th ('repeat') argument to PyRange_New().
Diffstat (limited to 'Doc')
| -rw-r--r-- | Doc/lib/libstdtypes.tex | 8 |
1 files changed, 2 insertions, 6 deletions
diff --git a/Doc/lib/libstdtypes.tex b/Doc/lib/libstdtypes.tex index f606d78..4f7e27a 100644 --- a/Doc/lib/libstdtypes.tex +++ b/Doc/lib/libstdtypes.tex @@ -775,12 +775,8 @@ xrange object will always take the same amount of memory, no matter the size of the range it represents. There are no consistent performance advantages. -XRange objects behave like tuples, and offer a single method: - -\begin{methoddesc}[xrange]{tolist}{} - Return a list object which represents the same values as the xrange - object. -\end{methoddesc} +XRange objects have very little behavior: they only support indexing +and the \function{len()} function. \subsubsection{Mutable Sequence Types \label{typesseq-mutable}} |