summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRaymond Hettinger <python@rcn.com>2002-12-11 07:14:03 (GMT)
committerRaymond Hettinger <python@rcn.com>2002-12-11 07:14:03 (GMT)
commitd2bef8256bf7ce6bea7a80074cbd021b5af154af (patch)
tree01f2b6099c00576e342fd4b85beaf1363029c0cd
parent39c7b4596483b6f6437667aa7bf5bb4f12d374f0 (diff)
downloadcpython-d2bef8256bf7ce6bea7a80074cbd021b5af154af.zip
cpython-d2bef8256bf7ce6bea7a80074cbd021b5af154af.tar.gz
cpython-d2bef8256bf7ce6bea7a80074cbd021b5af154af.tar.bz2
Update comments about the performance of xrange().
-rw-r--r--Doc/lib/libstdtypes.tex4
-rw-r--r--Objects/rangeobject.c4
2 files changed, 4 insertions, 4 deletions
diff --git a/Doc/lib/libstdtypes.tex b/Doc/lib/libstdtypes.tex
index 4372ec1..a104d85 100644
--- a/Doc/lib/libstdtypes.tex
+++ b/Doc/lib/libstdtypes.tex
@@ -884,8 +884,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 have very little behavior: they only support indexing
-and the \function{len()} function.
+XRange objects have very little behavior: they only support indexing,
+iteration, and the \function{len()} function.
\subsubsection{Mutable Sequence Types \label{typesseq-mutable}}
diff --git a/Objects/rangeobject.c b/Objects/rangeobject.c
index 9d0d9cd..9c7b74e 100644
--- a/Objects/rangeobject.c
+++ b/Objects/rangeobject.c
@@ -113,8 +113,8 @@ PyDoc_STRVAR(range_doc,
"xrange([start,] stop[, step]) -> xrange object\n\
\n\
Like range(), but instead of returning a list, returns an object that\n\
-generates the numbers in the range on demand. This is slightly slower\n\
-than range() but more memory efficient.");
+generates the numbers in the range on demand. For looping, this is \n\
+slightly faster than range() and more memory efficient.");
static PyObject *
range_item(rangeobject *r, int i)