Skip to content

[3.13] gh-74366: Fix the documentation of "$" in PyArg_ParseTupleAndKeywords() (GH-155301) #155310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
serhiy-storchaka merged 1 commit into from
Aug 7, 2026
+8 −3
Merged

[3.13] gh-74366: Fix the documentation of "$" in PyArg_ParseTupleAndKeywords() (GH-155301) #155310

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions Doc/c-api/arg.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -371,13 +371,18 @@ inside nested parentheses. They are:
their default value --- when an optional argument is not specified,
:c:func:`PyArg_ParseTuple` does not touch the contents of the corresponding C
variable(s).
For example, the format string ``"OO|OO"`` corresponds to the Python
signature ``f(a, b, c=None, d=None)``.

``$``
:c:func:`PyArg_ParseTupleAndKeywords` only:
Indicates that the remaining arguments in the Python argument list are
keyword-only. Currently, all keyword-only arguments must also be optional
arguments, so ``|`` must always be specified before ``$`` in the format
string.
keyword-only.
They are optional if ``|`` was specified before ``$``, and required otherwise.
``|`` cannot be specified after ``$``.
For example, the format string ``"O|O$O"`` corresponds to the Python
signature ``f(a, b=None, *, c=None)``,
and the format string ``"OO$OO"`` corresponds to ``f(a, b, *, c, d)``.

.. versionadded:: 3.3

Expand Down
Loading