summaryrefslogtreecommitdiff
path: root/Doc/lib/libcodeop.tex
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2006-05-03 02:04:40 +0000
committerFred Drake <fdrake@acm.org>2006-05-03 02:04:40 +0000
commitf25fa6ddb97979abe06fec961c22d8db0b6563a1 (patch)
tree8a615a1de9bebe4a04c8f7f8ff3098305dc1f744 /Doc/lib/libcodeop.tex
parentf863609cd64fef0fa0a36bd464096763c943f07e (diff)
downloadcpython-git-f25fa6ddb97979abe06fec961c22d8db0b6563a1.tar.gz
avoid ugly markup based on the unfortunate conversions of ">>" and "<<" to
guillemets; no need for magic here
Diffstat (limited to 'Doc/lib/libcodeop.tex')
-rw-r--r--Doc/lib/libcodeop.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/lib/libcodeop.tex b/Doc/lib/libcodeop.tex
index 7d6153e6b8..6972b6f5a3 100644
--- a/Doc/lib/libcodeop.tex
+++ b/Doc/lib/libcodeop.tex
@@ -19,7 +19,7 @@ There are two parts to this job:
\begin{enumerate}
\item Being able to tell if a line of input completes a Python
statement: in short, telling whether to print
- `\code{>\code{>}>~}' or `\code{...~}' next.
+ `\code{>>>~}' or `\code{...~}' next.
\item Remembering which future statements the user has entered, so
subsequent input can be compiled with these in effect.
\end{enumerate}