Mercurial > cpython-lru_cache-weakref
diff Doc/lib/libpdb.tex @ 7277:bf4e790bd61a legacy-trunk
Remove all \bcode / \ecode cruft; this is no longer needed. See previous
checkin of myformat.sty.
Change "\renewcommand{\indexsubitem}{(...)}" to "\setindexsubitem{(...)}"
everywhere.
Some other minor nits that I happened to come across.
| author | Fred Drake <fdrake@acm.org> |
|---|---|
| date | Fri, 13 Feb 1998 06:58:54 +0000 |
| parents | 1d0b9028523c |
| children | 621440bb98b9 |
line wrap: on
line diff
--- a/Doc/lib/libpdb.tex Fri Feb 13 06:48:05 1998 +0000 +++ b/Doc/lib/libpdb.tex Fri Feb 13 06:58:54 1998 +0000 @@ -2,7 +2,7 @@ \stmodindex{pdb} \index{debugging} -\renewcommand{\indexsubitem}{(in module pdb)} +\setindexsubitem{(in module pdb)} The module \code{pdb} defines an interactive source code debugger for Python programs. It supports setting @@ -29,7 +29,7 @@ The debugger's prompt is ``\code{(Pdb) }''. Typical usage to run a program under control of the debugger is: -\bcode\begin{verbatim} +\begin{verbatim} >>> import pdb >>> import mymodule >>> pdb.run('mymodule.test()') @@ -40,7 +40,7 @@ NameError: 'spam' > <string>(1)?() (Pdb) -\end{verbatim}\ecode +\end{verbatim} % \code{pdb.py} can also be invoked as a script to debug other scripts. For example: @@ -48,7 +48,7 @@ Typical usage to inspect a crashed program is: -\bcode\begin{verbatim} +\begin{verbatim} >>> import pdb >>> import mymodule >>> mymodule.test() @@ -63,7 +63,7 @@ > ./mymodule.py(3)test2() -> print spam (Pdb) -\end{verbatim}\ecode +\end{verbatim} % The module defines the following functions; each enters the debugger in a slightly different way: @@ -224,10 +224,10 @@ of the statement resembles a debugger command. To set a global variable, you can prefix the assignment command with a ``\code{global}'' command on the same line, e.g.: -\bcode\begin{verbatim} +\begin{verbatim} (Pdb) global list_options; list_options = ['-l'] (Pdb) -\end{verbatim}\ecode +\end{verbatim} % \item[q(uit)]
