diff options
| author | Greg Ward <gward@python.net> | 2005-07-22 01:54:54 (GMT) |
|---|---|---|
| committer | Greg Ward <gward@python.net> | 2005-07-22 01:54:54 (GMT) |
| commit | c0c8bb36adf36651cd58fb66a8e3ce02494c57e0 (patch) | |
| tree | 4e2b8fa3da87c1c60bb42e3b404fca81295640f6 | |
| parent | ba72589680bfc59bc699ca0051be617bb82758b8 (diff) | |
| download | cpython-c0c8bb36adf36651cd58fb66a8e3ce02494c57e0.zip cpython-c0c8bb36adf36651cd58fb66a8e3ce02494c57e0.tar.gz cpython-c0c8bb36adf36651cd58fb66a8e3ce02494c57e0.tar.bz2 | |
SF #1204347: typo fix.
| -rw-r--r-- | Doc/lib/liboptparse.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/lib/liboptparse.tex b/Doc/lib/liboptparse.tex index 5e7841d..547ac1d 100644 --- a/Doc/lib/liboptparse.tex +++ b/Doc/lib/liboptparse.tex @@ -584,7 +584,7 @@ foo 1.0 There are two broad classes of errors that \module{optparse} has to worry about: programmer errors and user errors. Programmer errors are usually -erroneous calls to \code{parse.add{\_}option()}, e.g. invalid option strings, +erroneous calls to \code{parser.add{\_}option()}, e.g. invalid option strings, unknown option attributes, missing option attributes, etc. These are dealt with in the usual way: raise an exception (either \code{optparse.OptionError} or \code{TypeError}) and let the program crash. @@ -1347,7 +1347,7 @@ parser.add_option("--novice", action="store_const", To avoid this confusion, use \method{set{\_}defaults()}: \begin{verbatim} -parse.set_defaults(mode="advanced") +parser.set_defaults(mode="advanced") parser.add_option("--advanced", action="store_const", dest="mode", const="advanced") parser.add_option("--novice", action="store_const", |