summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2003-07-16 03:26:31 (GMT)
committerFred Drake <fdrake@acm.org>2003-07-16 03:26:31 (GMT)
commit3605ae5966afdd58ebe95e26b457cf4b72fd86f2 (patch)
treea57cb931e9af001fe67167206e806c38e945d5c1
parent7769bb922483ef8ef461fcca8142b97fe50a3f11 (diff)
downloadcpython-3605ae5966afdd58ebe95e26b457cf4b72fd86f2.zip
cpython-3605ae5966afdd58ebe95e26b457cf4b72fd86f2.tar.gz
cpython-3605ae5966afdd58ebe95e26b457cf4b72fd86f2.tar.bz2
In the description of enumerate(), the indexing operators should not
be included in the \var. This produced weird results in general, but broke the GNU info conversion.
-rw-r--r--Doc/whatsnew/whatsnew23.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/whatsnew/whatsnew23.tex b/Doc/whatsnew/whatsnew23.tex
index 8b3fc61..fcaa563 100644
--- a/Doc/whatsnew/whatsnew23.tex
+++ b/Doc/whatsnew/whatsnew23.tex
@@ -383,8 +383,8 @@ and implemented by Jack Jansen.}
A new built-in function, \function{enumerate()}, will make
certain loops a bit clearer. \code{enumerate(thing)}, where
\var{thing} is either an iterator or a sequence, returns a iterator
-that will return \code{(0, \var{thing[0]})}, \code{(1,
-\var{thing[1]})}, \code{(2, \var{thing[2]})}, and so forth.
+that will return \code{(0, \var{thing}[0])}, \code{(1,
+\var{thing}[1])}, \code{(2, \var{thing}[2])}, and so forth.
Fairly often you'll see code to change every element of a list that
looks like this: