@@ -11,7 +11,7 @@ msgid ""
1111msgstr ""
1212"Project-Id-Version : Python 3.14\n "
1313"Report-Msgid-Bugs-To : \n "
14- "POT-Creation-Date : 2025-11-21 14:14 +0000\n "
14+ "POT-Creation-Date : 2025-11-25 14:15 +0000\n "
1515"PO-Revision-Date : 2025-09-16 00:00+0000\n "
1616"Last-Translator : python-doc bot, 2025\n "
1717"Language-Team : Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n "
@@ -1618,6 +1618,57 @@ msgid ""
16181618"See also :c:func:`PyEval_SetTrace` and :c:func:`PyEval_SetProfile` functions."
16191619msgstr ""
16201620
1621+ msgid ""
1622+ "Set the stack protection start address and stack protection size of a Python "
1623+ "thread state."
1624+ msgstr ""
1625+
1626+ msgid ""
1627+ "On success, return ``0``. On failure, set an exception and return ``-1``."
1628+ msgstr ""
1629+
1630+ msgid ""
1631+ "CPython implements :ref:`recursion control <recursion>` for C code by "
1632+ "raising :py:exc:`RecursionError` when it notices that the machine execution "
1633+ "stack is close to overflow. See for example the :c:func:"
1634+ "`Py_EnterRecursiveCall` function. For this, it needs to know the location of "
1635+ "the current thread's stack, which it normally gets from the operating "
1636+ "system. When the stack is changed, for example using context switching "
1637+ "techniques like the Boost library's ``boost::context``, you must call :c:"
1638+ "func:`~PyUnstable_ThreadState_SetStackProtection` to inform CPython of the "
1639+ "change."
1640+ msgstr ""
1641+
1642+ msgid ""
1643+ "Call :c:func:`~PyUnstable_ThreadState_SetStackProtection` either before or "
1644+ "after changing the stack. Do not call any other Python C API between the "
1645+ "call and the stack change."
1646+ msgstr ""
1647+
1648+ msgid ""
1649+ "See :c:func:`PyUnstable_ThreadState_ResetStackProtection` for undoing this "
1650+ "operation."
1651+ msgstr ""
1652+
1653+ msgid ""
1654+ "This function was added in a bugfix release, and extensions that use it will "
1655+ "be incompatible with Python 3.14.0. Most packaging tools for Python are not "
1656+ "able to handle this incompatibility automatically, and will need explicit "
1657+ "configuration. When using PyPA standards (wheels and source distributions), "
1658+ "specify ``Requires-Python: != 3.14.0.*`` in `core metadata <https://"
1659+ "packaging.python.org/en/latest/specifications/core-metadata/#requires-"
1660+ "python>`_."
1661+ msgstr ""
1662+
1663+ msgid ""
1664+ "Reset the stack protection start address and stack protection size of a "
1665+ "Python thread state to the operating system defaults."
1666+ msgstr ""
1667+
1668+ msgid ""
1669+ "See :c:func:`PyUnstable_ThreadState_SetStackProtection` for an explanation."
1670+ msgstr ""
1671+
16211672msgid "Get the current interpreter."
16221673msgstr ""
16231674
0 commit comments