From 059061a237d6b6358bc22f9257de3cbb0a523483 Mon Sep 17 00:00:00 2001 From: Victor Stinner Date: Mon, 18 Apr 2011 16:34:31 +0200 Subject: [PATCH] Issue #11768: signal.set_wakeup_fd() and PySignal_SetWakeupFd() added in 2.6 Fix the documentation. --- Doc/c-api/exceptions.rst | 2 ++ Doc/library/signal.rst | 2 ++ 2 files changed, 4 insertions(+) diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst index e9ced0bdb0d..8b1e8fc7fb9 100644 --- a/Doc/c-api/exceptions.rst +++ b/Doc/c-api/exceptions.rst @@ -347,6 +347,8 @@ is a separate error indicator for each thread. error checking. *fd* should be a valid file descriptor. The function should only be called from the main thread. + .. versionadded:: 2.6 + .. cfunction:: PyObject* PyErr_NewException(char *name, PyObject *base, PyObject *dict) diff --git a/Doc/library/signal.rst b/Doc/library/signal.rst index 74ff78d04b3..922911789cd 100644 --- a/Doc/library/signal.rst +++ b/Doc/library/signal.rst @@ -204,6 +204,8 @@ The :mod:`signal` module defines the following functions: attempting to call it from other threads will cause a :exc:`ValueError` exception to be raised. + .. versionadded:: 2.6 + .. function:: siginterrupt(signalnum, flag)