Lines Matching +full:human +full:- +full:signals
1 :mod:`signal` --- Set handlers for asynchronous events
9 --------------
15 -------------
29 On WebAssembly platforms ``wasm32-emscripten`` and ``wasm32-wasi``, signals
30 are emulated and therefore behave differently. Several functions and signals
36 A Python signal handler does not get executed inside the low-level (C) signal
37 handler. Instead, the low-level signal handler sets a flag which tells the
49 * A long-running calculation implemented purely in C (such as regular
51 arbitrary amount of time, regardless of any signals received. The Python
55 the main thread. See the :ref:`note below <handlers-and-exceptions>` for a
58 .. _signals-and-threads:
61 Signals and threads
65 even if the signal was received in another thread. This means that signals
66 can't be used as a means of inter-thread communication. You can use
73 ---------------
79 …:class:`enums <enum.IntEnum>` (:class:`Signals`, :class:`Handlers` and :class:`Sigmasks` respectiv…
81 :func:`sigwait` functions return human-readable
82 :class:`enums <enum.IntEnum>` as :class:`Signals` objects.
87 .. class:: Signals
168 Floating-point exception. For example, division by zero.
228 User-defined signal 1.
234 User-defined signal 2.
249 ':c:func:`signal`' lists the existing signals (on some systems this is
304 indicating that signals are to be blocked.
311 indicating that signals are to be unblocked.
342 If *time* is non-zero, this function requests that a :const:`SIGALRM` signal be
377 less than ``range(1, NSIG)`` if some signals are reserved by the system
422 thread of the main interpreter <signals-and-threads>`. Therefore, the only point of sending a
433 .. audit-event:: signal.pthread_kill thread_id,signalnum signal.pthread_kill
447 is the set of signals whose delivery is currently blocked for the caller.
448 Return the old signal mask as a set of signals.
452 * :data:`SIG_BLOCK`: The set of blocked signals is the union of the current
454 * :data:`SIG_UNBLOCK`: The signals in *mask* are removed from the current
455 set of blocked signals. It is permissible to attempt to unblock a
457 * :data:`SIG_SETMASK`: The set of blocked signals is set to the *mask*
462 mask including all signals.
485 is non-zero). The interval timer specified by *which* can be cleared by
516 The old wakeup fd is returned (or -1 if file descriptor wakeup was not
517 enabled). If *fd* is -1, file descriptor wakeup is disabled.
518 If not -1, *fd* must be non-blocking. It is up to the library to remove
522 from :ref:`the main thread of the main interpreter <signals-and-threads>`;
528 differ in how they determine *which* signal or signals have
534 limited amount of buffer space, and if too many signals arrive too
535 quickly, then the buffer may become full, and some signals may be
538 to be printed to stderr when signals are lost.
542 is whether the fd's buffer is empty or non-empty; a full buffer
577 from :ref:`the main thread of the main interpreter <signals-and-threads>`;
583 see the :ref:`description in the type hierarchy <frame-objects>` or see the
597 Examine the set of signals that are pending for delivery to the calling
598 thread (i.e., the signals which have been raised while blocked). Return the
599 set of the pending signals.
613 signals specified in the signal set *sigset*. The function accepts the signal
614 (removes it from the pending list of signals), and returns the signal number.
629 signals specified in the signal set *sigset*. The function accepts the
630 signal and removes it from the pending list of signals. If one of the
631 signals in *sigset* is already pending for the calling thread, the function
676 .. _signal-example:
679 --------
684 :func:`os.open` to hang indefinitely. The solution is to set a 5-second alarm
691 signame = signal.Signals(signum).name
695 # Set the signal handler and a 5-second alarm
705 ---------------
740 .. _handlers-and-exceptions:
743 --------------------------------------