@@ -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-02-13 14:37 +0000\n "
14+ "POT-Creation-Date : 2026-02-21 14:20 +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 "
@@ -619,37 +619,64 @@ msgstr ""
619619msgid "Signal Handling"
620620msgstr ""
621621
622- msgid "This function interacts with Python's signal handling."
622+ msgid ""
623+ "Handle external interruptions, such as signals or activating a debugger, "
624+ "whose processing has been delayed until it is safe to run Python code and/or "
625+ "raise exceptions."
626+ msgstr ""
627+
628+ msgid ""
629+ "For example, pressing :kbd:`Ctrl-C` causes a terminal to send the :py:data:"
630+ "`signal.SIGINT` signal. This function executes the corresponding Python "
631+ "signal handler, which, by default, raises the :exc:`KeyboardInterrupt` "
632+ "exception."
633+ msgstr ""
634+
635+ msgid ""
636+ ":c:func:`!PyErr_CheckSignals` should be called by long-running C code "
637+ "frequently enough so that the response appears immediate to humans."
638+ msgstr ""
639+
640+ msgid "Handlers invoked by this function currently include:"
623641msgstr ""
624642
625643msgid ""
626- "If the function is called from the main thread and under the main Python "
627- "interpreter, it checks whether a signal has been sent to the processes and "
628- "if so, invokes the corresponding signal handler. If the :mod:`signal` "
629- "module is supported, this can invoke a signal handler written in Python."
644+ "Signal handlers, including Python functions registered using the :mod:"
645+ "`signal` module."
630646msgstr ""
631647
632648msgid ""
633- "The function attempts to handle all pending signals, and then returns ``0``. "
634- "However, if a Python signal handler raises an exception, the error indicator "
635- "is set and the function returns ``-1`` immediately (such that other pending "
636- "signals may not have been handled yet: they will be on the next :c:func:"
637- "`PyErr_CheckSignals()` invocation)."
649+ "Signal handlers are only run in the main thread of the main interpreter."
638650msgstr ""
639651
640652msgid ""
641- "If the function is called from a non-main thread, or under a non-main Python "
642- "interpreter, it does nothing and returns ``0``."
653+ "(This is where the function got the name: originally, signals were the only "
654+ "way to interrupt the interpreter.)"
655+ msgstr ""
656+
657+ msgid "Running the garbage collector, if necessary."
658+ msgstr ""
659+
660+ msgid "Executing a pending :ref:`remote debugger <remote-debugging>` script."
643661msgstr ""
644662
645663msgid ""
646- "This function can be called by long-running C code that wants to be "
647- "interruptible by user requests (such as by pressing Ctrl-C)."
664+ "If any handler raises an exception, immediately return ``-1`` with that "
665+ "exception set. Any remaining interruptions are left to be processed on the "
666+ "next :c:func:`PyErr_CheckSignals()` invocation, if appropriate."
667+ msgstr ""
668+
669+ msgid ""
670+ "If all handlers finish successfully, or there are no handlers to run, return "
671+ "``0``."
672+ msgstr ""
673+
674+ msgid "This function may now invoke the garbage collector."
648675msgstr ""
649676
650677msgid ""
651- "The default Python signal handler for :c:macro:`!SIGINT` raises the :exc: "
652- "`KeyboardInterrupt` exception ."
678+ "This function may now execute a remote debugger script, if remote debugging "
679+ "is enabled ."
653680msgstr ""
654681
655682msgid ""
0 commit comments