From 3a946f108152efc3b36f9ef22aa52ebe13b77d08 Mon Sep 17 00:00:00 2001 From: Savannah Ostrowski Date: Thu, 11 Dec 2025 09:42:36 -0800 Subject: [PATCH] Use subcommand over sub-command in argparse docs (GH-142488) (cherry picked from commit 387f88cac1e911672f6321f4fbb0a3af9710626d) Co-authored-by: Savannah Ostrowski --- 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 f64ace037f6975..413920ef1e1732 100644 --- a/Doc/library/argparse.rst +++ b/Doc/library/argparse.rst @@ -1669,7 +1669,7 @@ The Namespace object Other utilities --------------- -Sub-commands +Subcommands ^^^^^^^^^^^^ .. method:: ArgumentParser.add_subparsers(*, [title], [description], [prog], \ @@ -1698,7 +1698,7 @@ Sub-commands * *description* - description for the sub-parser group in help output, by default ``None`` - * *prog* - usage information that will be displayed with sub-command help, + * *prog* - usage information that will be displayed with subcommand help, by default the name of the program and any positional arguments before the subparser argument @@ -1708,7 +1708,7 @@ Sub-commands * action_ - the basic type of action to be taken when this argument is encountered at the command line - * dest_ - name of the attribute under which sub-command name will be + * dest_ - name of the attribute under which subcommand name will be stored; by default ``None`` and no value is stored * required_ - Whether or not a subcommand must be provided, by default