From 77e543c6cdd40debd215fa6e913fcc64c0748eb0 Mon Sep 17 00:00:00 2001 From: Berker Peksag Date: Sun, 24 Apr 2016 02:59:16 +0300 Subject: [PATCH] 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. --- Doc/library/signal.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Doc/library/signal.rst b/Doc/library/signal.rst index 98eb7fdf20..d02a0a8e3c 100644 --- a/Doc/library/signal.rst +++ b/Doc/library/signal.rst @@ -351,6 +351,9 @@ The :mod:`signal` module defines the following functions: On Windows, :func:`signal` can only be called with :const:`SIGABRT`, :const:`SIGFPE`, :const:`SIGILL`, :const:`SIGINT`, :const:`SIGSEGV`, or :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() -- 2.40.0