gh-84116: Docs: Document help and aliases for argparse.add_parser()

Doc/howto/free-threading-python.rst

@@ -116,12 +116,12 @@ after the main thread is running.  The following objects are immortalized:
 * :ref:`classes <classes>` (type objects)
 
 Because immortal objects are never deallocated, applications that create many
-objects of these types may see increased memory usage.  This is expected to be
-addressed in the 3.14 release.
+objects of these types may see increased memory usage. Work to further reduce
+this overhead continued in the 3.14 release.
 
 Additionally, numeric and string literals in the code as well as strings
-returned by :func:`sys.intern` are also immortalized.  This behavior is
-expected to remain in the 3.14 free-threaded build.
+returned by :func:`sys.intern` are also immortalized.  This behavior remains
+in the 3.14 free-threaded build.
 
 
 Frame objects
@@ -152,9 +152,10 @@ Programs that spend most of their time in C extensions or I/O will see
 less of an impact.  The largest impact is because the specializing adaptive
 interpreter (:pep:`659`) is disabled in the free-threaded build.  We expect
 to re-enable it in a thread-safe way in the 3.14 release.  This overhead is
-expected to be reduced in upcoming Python release.   We are aiming for an
-overhead of 10% or less on the pyperformance suite compared to the default
-GIL-enabled build.
+expected to be reduced in upcoming Python release. This overhead was reduced
+in the 3.14 release. Reducing overhead further remains an active development goal,
+with an aim for 10% or less on the pyperformance suite compared to the default GIL-enabled
+build.
 
 
 Behavioral changes

Doc/library/argparse.rst

@@ -1664,7 +1664,7 @@
                                           [dest], [required], \
                                           [help], [metavar])
 
    Many programs split up their functionality into a number of subcommands,
    for example, the ``svn`` program can invoke subcommands like ``svn
    checkout``, ``svn update``, and ``svn commit``.  Splitting up functionality
    this way can be a particularly good idea when a program performs several
@@ -1672,10 +1672,24 @@
    :class:`ArgumentParser` supports the creation of such subcommands with the
    :meth:`!add_subparsers` method.  The :meth:`!add_subparsers` method is normally
    called with no arguments and returns a special action object.  This object
-   has a single method, :meth:`~_SubParsersAction.add_parser`, which takes a
-   command name and any :class:`!ArgumentParser` constructor arguments, and
-   returns an :class:`!ArgumentParser` object that can be modified as usual.
-
+   has a single method, :meth:`~_SubParsersAction.add_parser`:
+   .. method:: _SubParsersAction.add_parser(name, *, help=None, aliases=None, **kwargs)
+
+   Creates and returns a new :class:`!ArgumentParser` object for the
+   subcommand *name*.
+
+   :param name: The name of the sub-command.
+   :param help: A short description for this sub-command. If provided,
+                it will be listed next to the command in the main
+                parser's help message (e.g., ``PROG --help``).
+   :param aliases: A list or sequence of strings that can be used as
+                   alternative names for this sub-command (e.g., ``aliases=['r']``
+                   for a ``'run'`` command).
+   :param kwargs: All other keyword arguments are passed directly to the
+                  :class:`!ArgumentParser` constructor.
+
+   This returned :class:`!ArgumentParser` object can be modified as usual.
+
    Description of parameters:
 
    * *title* - title for the sub-parser group in help output; by default

Misc/NEWS.d/next/Documentation/2025-10-25-00-49-43.gh-issue-140281.tuMQUe.rst

@@ -0,0 +1 @@
+Update the free-threading how-to guide for 3.14 status.

Misc/NEWS.d/next/Documentation/2025-10-25-14-08-42.gh-issue-84116.lKcoHw.rst

@@ -0,0 +1,3 @@
+Document ``help`` and ``aliases`` parameters for
+:meth:`argparse._SubParsersAction.add_parser` in the :mod:`argparse`
+documentation.