Issue #25314: Remove confused statement about const argument
This commit is contained in:
parent
d82da9f7f2
commit
b4912b8ed3
|
@ -720,8 +720,7 @@ how the command-line arguments should be handled. The supplied actions are:
|
||||||
Namespace(foo='1')
|
Namespace(foo='1')
|
||||||
|
|
||||||
* ``'store_const'`` - This stores the value specified by the const_ keyword
|
* ``'store_const'`` - This stores the value specified by the const_ keyword
|
||||||
argument. (Note that the const_ keyword argument defaults to the rather
|
argument. The ``'store_const'`` action is most commonly used with
|
||||||
unhelpful ``None``.) The ``'store_const'`` action is most commonly used with
|
|
||||||
optional arguments that specify some sort of flag. For example::
|
optional arguments that specify some sort of flag. For example::
|
||||||
|
|
||||||
>>> parser = argparse.ArgumentParser()
|
>>> parser = argparse.ArgumentParser()
|
||||||
|
@ -923,7 +922,8 @@ the various :class:`ArgumentParser` actions. The two most common uses of it are
|
||||||
command-line argument following it, the value of ``const`` will be assumed instead.
|
command-line argument following it, the value of ``const`` will be assumed instead.
|
||||||
See the nargs_ description for examples.
|
See the nargs_ description for examples.
|
||||||
|
|
||||||
The ``const`` keyword argument defaults to ``None``.
|
With the ``'store_const'`` and ``'append_const'`` actions, the ``const``
|
||||||
|
keyword argument must be given. For other actions, is defaults to ``None``.
|
||||||
|
|
||||||
|
|
||||||
default
|
default
|
||||||
|
|
Loading…
Reference in New Issue