]> granicus.if.org Git - python/commitdiff
Remove note that PyErr_SetInterrupt() is obsolete; add comment about the
authorFred Drake <fdrake@acm.org>
Thu, 25 Mar 2004 14:25:28 +0000 (14:25 +0000)
committerFred Drake <fdrake@acm.org>
Thu, 25 Mar 2004 14:25:28 +0000 (14:25 +0000)
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

index f98b644896c219157fc97243f4fe69ce6aeeeeb1..3a51a05bf56f373d36451be9cd02f4ce421a2d9c 100644 (file)
@@ -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,