@@ -673,36 +673,8 @@ Signal Handling
673673 single: SIGINT (C macro)
674674 single: KeyboardInterrupt (built-in exception)
675675
676- This function interacts with Python's signal handling.
677676
678- If the function is called from the main thread and under the main Python
679- interpreter, it checks whether a signal has been sent to the processes
680- and if so, invokes the corresponding signal handler. If the :mod: `signal `
681- module is supported, this can invoke a signal handler written in Python.
682677
683- The function attempts to handle all pending signals, and then returns ``0 ``.
684- However, if a Python signal handler raises an exception, the error
685- indicator is set and the function returns ``-1 `` immediately (such that
686- other pending signals may not have been handled yet: they will be on the
687- next :c:func: `PyErr_CheckSignals() ` invocation).
688-
689- This function may invoke the garbage collector or execute a :ref:`remote
690- debugger <remote-debugging>` script, regardless of the calling thread
691- or Python interpreter.
692-
693- This function can be called by long-running C code that wants to
694- be interruptible by user requests (such as by pressing Ctrl-C).
695-
696- .. note::
697- The default Python signal handler for :c:macro:`!SIGINT` raises the
698- :exc:`KeyboardInterrupt` exception.
699-
700- .. versionchanged:: 3.12
701- This function may now invoke the garbage collector.
702-
703- .. versionchanged:: 3.14
704- This function may now execute a remote debugger script, if remote
705- debugging is enabled.
706678 Handle external interruptions, such as signals (including :kbd: `Ctrl - C `),
707679 or activating a debugger, whose processing has been delayed until it is safe
708680 to run Python code and/or raise exceptions.
0 commit comments