Docs: Use arguments to replace args in argparse.rst

[Yzi-Li]

---

📚 Documentation preview 📚: https://cpython-previews--135510.org.readthedocs.build/

[StanFromIreland]

Should this be done, it is a bit churny, though it also has benefits, and aligns with other current devguide guidelines (i.e. don't use Latin abbreviations)? This is not a single occurrence, however:

c-api/call.rst:the arguments to an args tuple and kwargs dict anyway, then there is no point
c-api/call.rst:| Function                                 | callable         | args               | kwargs        |
library/tkinter.ttk.rst:      is specified then it is called with args if widget state matches
library/imaplib.rst:   Execute command args with messages identified by UID, rather than message
library/queue.rst:   Put *item* into the queue.  If optional args *block* is true and *timeout* is
library/queue.rst:   Remove and return an item from the queue.  If optional args *block* is true and
library/queue.rst:   The optional args *block* and *timeout* are ignored and only provided
library/queue.rst:   Remove and return an item from the queue.  If optional args *block* is true and
library/cmd.rst:   completing of commands args is done by calling :meth:`!complete_foo` with
library/string.rst:      passed to vformat.  The set of unused args can be calculated from these
library/argparse.rst:* ``'+'``. Just like ``'*'``, all command-line args present are gathered into a
library/argparse.rst:     >>> # parse the args and call whatever function was selected
library/argparse.rst:     >>> # parse the args and call whatever function was selected
library/unittest.mock-examples.rst:``side_effect`` will be called with the same args as the mock. This gives us an
library/multiprocessing.rst:      Remove and return an item from the queue.  If optional args *block* is
library/test.rst:   *kw* is extra keyword args to pass to :func:`subprocess.Popen`. Returns a
tutorial/errors.rst:   ...     print(inst)          # __str__ allows args to be printed directly,
using/configure.rst:   optimization configure args + the CPU architecture, and not all combinations

[Yzi-Li]

Just in this file (argparse.rst), only this one needs to be changed. ">>> # parse the args and call whatever function was selected" is a comment, "args" refer to the variable args.

OTOH, we use "All command-line arguments present are gathered into a list." just in the previous item *.

[ZeroIntensity]

I think this is worth doing. If there are more occurences of this, let's make an issue and do it in a broader manner. But for now, I'll land this. Thanks!

[miss-islington-app]

Thanks @Yzi-Li for the PR, and @ZeroIntensity for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14.
🐍🍒⛏🤖

[bedevere-app]

GH-135866 is a backport of this pull request to the 3.14 branch.

[bedevere-app]

GH-135867 is a backport of this pull request to the 3.13 branch.