summaryrefslogtreecommitdiff
path: root/Doc
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2004-02-12 14:35:18 +0000
committerFred Drake <fdrake@acm.org>2004-02-12 14:35:18 +0000
commit892f9f8046ed786c6c5d62725726132bed91309e (patch)
tree7f2807a2f23d53474a72f6e568429a408220516c /Doc
parent1b8a821698937d0a0906e58d9e5f3c6d985db574 (diff)
downloadcpython-892f9f8046ed786c6c5d62725726132bed91309e.tar.gz
fix minor markup error: \code{for} --> \keyword{for}
Diffstat (limited to 'Doc')
-rw-r--r--Doc/tut/tut.tex13
1 files changed, 7 insertions, 6 deletions
diff --git a/Doc/tut/tut.tex b/Doc/tut/tut.tex
index 3933fc6b65..7814231e7d 100644
--- a/Doc/tut/tut.tex
+++ b/Doc/tut/tut.tex
@@ -4286,7 +4286,7 @@ finally the instance converted to a string using the built-in function
\section{Iterators\label{iterators}}
By now, you've probably noticed that most container objects can be looped
-over using a \code{for} statement:
+over using a \keyword{for} statement:
\begin{verbatim}
for element in [1, 2, 3]:
@@ -4302,11 +4302,12 @@ for line in open("myfile.txt"):
\end{verbatim}
This style of access is clear, concise, and convenient. The use of iterators
-pervades and unifies Python. Behind the scenes, the \code{for} statement calls
-\function{iter()} on the container object. The function returns an iterator
-object that defines the method \method{next()} which accesses elements in the
-container one at a time. When there are no more elements, \method{next()}
-raises a \exception{StopIteration} exception which tells the \code{for} loop
+pervades and unifies Python. Behind the scenes, the \keyword{for}
+statement calls \function{iter()} on the container object. The
+function returns an iterator object that defines the method
+\method{next()} which accesses elements in the container one at a
+time. When there are no more elements, \method{next()} raises a
+\exception{StopIteration} exception which tells the \keyword{for} loop
to terminate. This example shows how it all works:
\begin{verbatim}