From 85309512ec4f461a3025fab3bd11408950752f5d Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Thu, 25 Mar 2004 14:25:28 +0000 Subject: Remove note that PyErr_SetInterrupt() is obsolete; add comment about the fact that it was marked obsolete but is still needed. Closes SF bug #919299. Someone else should backport this to Python 2.3. --- Doc/api/exceptions.tex | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Doc/api/exceptions.tex b/Doc/api/exceptions.tex index f98b644..3a51a05 100644 --- a/Doc/api/exceptions.tex +++ b/Doc/api/exceptions.tex @@ -299,12 +299,14 @@ for each thread. \end{cfuncdesc} \begin{cfuncdesc}{void}{PyErr_SetInterrupt}{} - This function is obsolete. It simulates the effect of a + It simulates the effect of a \constant{SIGINT}\ttindex{SIGINT} signal arriving --- the next time \cfunction{PyErr_CheckSignals()} is called, \withsubitem{(built-in exception)}{\ttindex{KeyboardInterrupt}} \exception{KeyboardInterrupt} will be raised. It may be called without holding the interpreter lock. + % XXX This was described as obsolete, but is used in + % thread.interrupt_main() (used from IDLE), so it's still needed. \end{cfuncdesc} \begin{cfuncdesc}{PyObject*}{PyErr_NewException}{char *name, -- cgit v0.12