@@ -11,7 +11,7 @@ msgid ""
1111msgstr ""
1212"Project-Id-Version : Python 3.14\n "
1313"Report-Msgid-Bugs-To : \n "
14- "POT-Creation-Date : 2026-07-31 16:48 +0000\n "
14+ "POT-Creation-Date : 2026-08-07 15:50 +0000\n "
1515"PO-Revision-Date : 2026-05-08 17:16+0000\n "
1616"Last-Translator : Rafael Fontenelle <rffontenelle@gmail.com>, 2026\n "
1717"Language-Team : Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n "
@@ -636,17 +636,20 @@ msgid ""
636636"optional. The C variables corresponding to optional arguments should be "
637637"initialized to their default value --- when an optional argument is not "
638638"specified, :c:func:`PyArg_ParseTuple` does not touch the contents of the "
639- "corresponding C variable(s)."
639+ "corresponding C variable(s). For example, the format string ``\" OO|OO\" `` "
640+ "corresponds to the Python signature ``f(a, b, c=None, d=None)``."
640641msgstr ""
641642
642643msgid "``$``"
643644msgstr "``$``"
644645
645646msgid ""
646647":c:func:`PyArg_ParseTupleAndKeywords` only: Indicates that the remaining "
647- "arguments in the Python argument list are keyword-only. Currently, all "
648- "keyword-only arguments must also be optional arguments, so ``|`` must always "
649- "be specified before ``$`` in the format string."
648+ "arguments in the Python argument list are keyword-only. They are optional if "
649+ "``|`` was specified before ``$``, and required otherwise. ``|`` cannot be "
650+ "specified after ``$``. For example, the format string ``\" O|O$O\" `` "
651+ "corresponds to the Python signature ``f(a, b=None, *, c=None)``, and the "
652+ "format string ``\" OO$OO\" `` corresponds to ``f(a, b, *, c, d)``."
650653msgstr ""
651654
652655msgid "``:``"
0 commit comments