From 456ff916647d43c20e51ed14f139e9c26296d3c2 Mon Sep 17 00:00:00 2001
From: Edward Loper <edloper@gradient.cis.upenn.edu>
Date: Mon, 27 Sep 2004 03:30:44 +0000
Subject: [PATCH] - Fixed typo in multi-line exception example - Fixed
 indentation for a verbatim block

---
 Doc/lib/libdoctest.tex | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/Doc/lib/libdoctest.tex b/Doc/lib/libdoctest.tex
index 23818806bc..81a472ce07 100644
--- a/Doc/lib/libdoctest.tex
+++ b/Doc/lib/libdoctest.tex
@@ -443,7 +443,7 @@ last line of a traceback, but can extend across multiple lines if the
 exception has a multi-line detail:
 
 \begin{verbatim}
->>> raise ValueError('multi\n   line\ndetail')
+>>> raise ValueError('multi\n    line\ndetail')
 Traceback (most recent call last):
   File "<stdin>", line 1, in ?
 ValueError: multi
@@ -460,7 +460,7 @@ significant documentation value to the example.  So the last example
 is probably better as:
 
 \begin{verbatim}
->>> raise ValueError('multi\n   line\ndetail')
+>>> raise ValueError('multi\n    line\ndetail')
 Traceback (most recent call last):
     ...
 ValueError: multi
@@ -1699,10 +1699,10 @@ the synthesized code under the debugger:
    \function{script_from_examples()} above.  For example, if module
    \file{a.py} contains a top-level function \function{f()}, then
 
-    \begin{verbatim}
-    import a, doctest
-    print doctest.testsource(a, "a.f")
-    \end{verbatim}
+\begin{verbatim}
+import a, doctest
+print doctest.testsource(a, "a.f")
+\end{verbatim}
 
   prints a script version of function \function{f()}'s docstring,
   with doctests converted to code, and the rest placed in comments.
-- 
2.50.0