Issue #11768: signal.set_wakeup_fd() and PySignal_SetWakeupFd() added in 2.6

Fix the documentation.

diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst
index e9ced0bdb0d9485c0afa37f94bda2c14886dea83..8b1e8fc7fb96cbf5a9d13c1425242b914cc98379 100644 (file)
--- 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 74ff78d04b3ee9f9e38076406d53dcfbce90bcd1..922911789cd3ed28bbcb172ecf516e5466453a23 100644 (file)
--- 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)