From 2e3d9d66a0bffb2555fb347694871b9c5c3c2ae8 Mon Sep 17 00:00:00 2001 From: PrinceNaroliya Date: Wed, 17 Sep 2025 20:45:57 +0530 Subject: [PATCH] gh-137988: Fix const description in argparse.add_argument() docs (GH-138315) (cherry picked from commit 37425fe9fb776f2bd3c8ec13cf7f16e04a71ea93) Co-authored-by: PrinceNaroliya Co-authored-by: Savannah Bailey --- Doc/library/argparse.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/library/argparse.rst b/Doc/library/argparse.rst index 79e15994491eff..ef8242f5f780f5 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