From b4912b8ed367e540ee060fe912f841cc764fd293 Mon Sep 17 00:00:00 2001 From: Martin Panter Date: Sat, 9 Apr 2016 03:49:48 +0000 Subject: [PATCH] Issue #25314: Remove confused statement about const argument --- Doc/library/argparse.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/library/argparse.rst b/Doc/library/argparse.rst index 785ecbf44b5..6181ee2c7a6 100644 --- a/Doc/library/argparse.rst +++ b/Doc/library/argparse.rst @@ -720,8 +720,7 @@ how the command-line arguments should be handled. The supplied 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 + argument. The ``'store_const'`` action is most commonly used with optional arguments that specify some sort of flag. For example:: >>> 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. 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