Kaydet (Commit) 77e543c6 authored tarafından Berker Peksag's avatar Berker Peksag

Issue #21382: Clarify signal.signal() documentation on Windows

All signal.SIG* constants may not be defined on Windows so a call like

    signal.signal(signal.SIGPIPE, lambda signum, frame: sys.exit(1))

will raise an AttributeError.
üst 02698283
...@@ -351,6 +351,9 @@ The :mod:`signal` module defines the following functions: ...@@ -351,6 +351,9 @@ The :mod:`signal` module defines the following functions:
On Windows, :func:`signal` can only be called with :const:`SIGABRT`, On Windows, :func:`signal` can only be called with :const:`SIGABRT`,
:const:`SIGFPE`, :const:`SIGILL`, :const:`SIGINT`, :const:`SIGSEGV`, or :const:`SIGFPE`, :const:`SIGILL`, :const:`SIGINT`, :const:`SIGSEGV`, or
:const:`SIGTERM`. A :exc:`ValueError` will be raised in any other case. :const:`SIGTERM`. A :exc:`ValueError` will be raised in any other case.
Note that not all systems define the same set of signal names; an
:exc:`AttributeError` will be raised if a signal name is not defined as
``SIG*`` module level constant.
.. function:: sigpending() .. function:: sigpending()
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment