#11904-#11905: Merge typo fixes with 3.2.
This commit is contained in:
commit
7817e3b151
|
@ -598,7 +598,7 @@ The add_argument() method
|
|||
has its own more detailed description below, but in short they are:
|
||||
|
||||
* `name or flags`_ - Either a name or a list of option strings, e.g. ``foo``
|
||||
or ``-f, --foo``
|
||||
or ``-f, --foo``.
|
||||
|
||||
* action_ - The basic type of action to be taken when this argument is
|
||||
encountered at the command line.
|
||||
|
@ -667,7 +667,7 @@ them, though most actions simply add an attribute to the object returned by
|
|||
command-line args should be handled. The supported actions are:
|
||||
|
||||
* ``'store'`` - This just stores the argument's value. This is the default
|
||||
action. For example::
|
||||
action. For example::
|
||||
|
||||
>>> parser = argparse.ArgumentParser()
|
||||
>>> parser.add_argument('--foo')
|
||||
|
@ -675,9 +675,9 @@ command-line args should be handled. The supported actions are:
|
|||
Namespace(foo='1')
|
||||
|
||||
* ``'store_const'`` - This stores the value specified by the const_ keyword
|
||||
argument. (Note that the const_ keyword argument defaults to the rather
|
||||
unhelpful ``None``.) The ``'store_const'`` action is most commonly used with
|
||||
optional arguments that specify some sort of flag. For example::
|
||||
argument. (Note that the const_ keyword argument defaults to the rather
|
||||
unhelpful ``None``.) The ``'store_const'`` action is most commonly used with
|
||||
optional arguments that specify some sort of flag. For example::
|
||||
|
||||
>>> parser = argparse.ArgumentParser()
|
||||
>>> parser.add_argument('--foo', action='store_const', const=42)
|
||||
|
|
Loading…
Reference in New Issue