summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2001-04-13 17:25:38 (GMT)
committerFred Drake <fdrake@acm.org>2001-04-13 17:25:38 (GMT)
commitc054c755820995e557b060d53aa432bec32fb2fe (patch)
tree34689cdd265c99e982f8b94950d2b69bf844b5ba
parent705088e65f67fa242802036ee129972b6d6fda63 (diff)
downloadcpython-c054c755820995e557b060d53aa432bec32fb2fe.zip
cpython-c054c755820995e557b060d53aa432bec32fb2fe.tar.gz
cpython-c054c755820995e557b060d53aa432bec32fb2fe.tar.bz2
Work around the conversion of ">>" and "<<" to guillemets. Reported by Ping.
-rw-r--r--Doc/inst/inst.tex2
-rw-r--r--Doc/lib/libdis.tex2
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/inst/inst.tex b/Doc/inst/inst.tex
index fafcc64..c051e68 100644
--- a/Doc/inst/inst.tex
+++ b/Doc/inst/inst.tex
@@ -364,7 +364,7 @@ running Python in interactive mode and typing a few simple commands.
Under \UNIX, just type \code{python} at the shell prompt; under Windows,
run ``Python 2.0 (interpreter)'' \XXX{right?}; under MacOS, \XXX{???}.
Once the interpreter is started, you type Python code at the
-\samp{>>> } prompt. For example, on my Linux system, I type the three
+\samp{>\code{>}> } prompt. For example, on my Linux system, I type the three
Python statements shown below, and get the output as shown, to find
out my \filevar{prefix} and \filevar{exec-prefix}:
diff --git a/Doc/lib/libdis.tex b/Doc/lib/libdis.tex
index 3a274ef..b41b719 100644
--- a/Doc/lib/libdis.tex
+++ b/Doc/lib/libdis.tex
@@ -56,7 +56,7 @@ was provided. The output is divided in the following columns:
\begin{enumerate}
\item the current instruction, indicated as \samp{-->},
-\item a labelled instruction, indicated with \samp{>>},
+\item a labelled instruction, indicated with \samp{>\code{>}},
\item the address of the instruction,
\item the operation code name,
\item operation parameters, and