From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Wed, 17 Sep 2025 15:51:30 +0000 (+0200) Subject: [3.14] gh-137988: Fix const description in argparse.add_argument() docs (GH-138315... X-Git-Tag: v3.14.0rc3~4 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=9d0ca237af669ffde8c97b628c16b51792b5a3b6;p=thirdparty%2FPython%2Fcpython.git [3.14] gh-137988: Fix const description in argparse.add_argument() docs (GH-138315) (#139051) Co-authored-by: PrinceNaroliya Co-authored-by: Savannah Bailey --- diff --git a/Doc/library/argparse.rst b/Doc/library/argparse.rst index 79e15994491e..ef8242f5f780 100644 --- a/Doc/library/argparse.rst +++ b/Doc/library/argparse.rst @@ -981,8 +981,8 @@ the various :class:`ArgumentParser` actions. The two most common uses of it are (like ``-f`` or ``--foo``) and ``nargs='?'``. This creates an optional argument that can be followed by zero or one command-line arguments. When parsing the command line, if the option string is encountered with no - command-line argument following it, the value of ``const`` will be assumed to - be ``None`` instead. See the nargs_ description for examples. + command-line argument following it, the value from ``const`` will be used. + See the nargs_ description for examples. .. versionchanged:: 3.11 ``const=None`` by default, including when ``action='append_const'`` or