From 8514b85edc420aa1f91c443e7e11629855a170d3 Mon Sep 17 00:00:00 2001 From: Georg Brandl Date: Tue, 1 Sep 2009 08:06:03 +0000 Subject: [PATCH] #6638: fix wrong parameter name and markup a class. --- Doc/library/optparse.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Doc/library/optparse.rst b/Doc/library/optparse.rst index 49371bea5d..2fa4388c21 100644 --- a/Doc/library/optparse.rst +++ b/Doc/library/optparse.rst @@ -1171,19 +1171,20 @@ where the input parameters are the list of arguments to process (default: ``sys.argv[1:]``) ``values`` - object to store option arguments in (default: a new instance of optparse.Values) + object to store option arguments in (default: a new instance of + :class:`optparse.Values`) and the return values are ``options`` - the same object that was passed in as ``options``, or the optparse.Values + the same object that was passed in as ``values``, or the optparse.Values instance created by :mod:`optparse` ``args`` the leftover positional arguments after all options have been processed The most common usage is to supply neither keyword argument. If you supply -``options``, it will be modified with repeated ``setattr()`` calls (roughly one +``values``, it will be modified with repeated ``setattr()`` calls (roughly one for every option argument stored to an option destination) and returned by :meth:`parse_args`. -- 2.50.1