From: Fred Drake <fdrake@acm.org>
Date: Thu, 17 May 2007 19:29:43 +0000 (+0000)
Subject: fix argument name in documentation; match the implementation
X-Git-Tag: v2.5.2c1~294
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2cb077a8c1b6436cb2c86178d6eb33fd4e6cd59e;p=python

fix argument name in documentation; match the implementation
---

diff --git a/Doc/lib/liboptparse.tex b/Doc/lib/liboptparse.tex
index df96dd4ae7..a33760bc65 100644
--- a/Doc/lib/liboptparse.tex
+++ b/Doc/lib/liboptparse.tex
@@ -1191,14 +1191,14 @@ OptionValueError if an invalid string is given.
 The whole point of creating and populating an OptionParser is to call
 its \method{parse{\_}args()} method:
 \begin{verbatim}
-(options, args) = parser.parse_args(args=None, options=None)
+(options, args) = parser.parse_args(args=None, values=None)
 \end{verbatim}
 
 where the input parameters are
 \begin{description}
 \item[\code{args}]
 the list of arguments to process (default: \code{sys.argv{[}1:]})
-\item[\code{options}]
+\item[\code{values}]
 object to store option arguments in (default: a new instance of
 optparse.Values)
 \end{description}