From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Tue, 15 Oct 2024 16:09:55 +0000 (+0200)
Subject: [3.12] gh-89819: Add argument_default and conflict_handler to add_argument_group... 
X-Git-Tag: v3.12.8~201
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=1cab726622985a5596529521f471aea8588747c3;p=thirdparty%2FPython%2Fcpython.git

[3.12] gh-89819: Add argument_default and conflict_handler to add_argument_group() docs (GH-125379) (GH-125539)

(cherry picked from commit c9826c11db25e81b1a90c837f84074879f1b1126)

Co-authored-by: Savannah Ostrowski <savannahostrowski@gmail.com>
---

diff --git a/Doc/library/argparse.rst b/Doc/library/argparse.rst
index a1f08ea27293..87d9a45539a1 100644
--- a/Doc/library/argparse.rst
+++ b/Doc/library/argparse.rst
@@ -1740,7 +1740,8 @@ FileType objects
 Argument groups
 ^^^^^^^^^^^^^^^
 
-.. method:: ArgumentParser.add_argument_group(title=None, description=None)
+.. method:: ArgumentParser.add_argument_group(title=None, description=None, *, \
+                                              [argument_default], [conflict_handler])
 
    By default, :class:`ArgumentParser` groups command-line arguments into
    "positional arguments" and "options" when displaying help
@@ -1785,6 +1786,11 @@ Argument groups
 
        --bar BAR  bar help
 
+   The optional, keyword-only parameters argument_default_ and conflict_handler_
+   allow for finer-grained control of the behavior of the argument group. These
+   parameters have the same meaning as in the :class:`ArgumentParser` constructor,
+   but apply specifically to the argument group rather than the entire parser.
+
    Note that any arguments not in your user-defined groups will end up back
    in the usual "positional arguments" and "optional arguments" sections.