Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 8530951

Browse files
committed
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.
1 parent bc503d1 commit 8530951

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

Doc/api/exceptions.tex

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -299,12 +299,14 @@ \chapter{Exception Handling \label{exceptionHandling}}
299299
\end{cfuncdesc}
300300

301301
\begin{cfuncdesc}{void}{PyErr_SetInterrupt}{}
302-
This function is obsolete. It simulates the effect of a
302+
It simulates the effect of a
303303
\constant{SIGINT}\ttindex{SIGINT} signal arriving --- the next time
304304
\cfunction{PyErr_CheckSignals()} is called,
305305
\withsubitem{(built-in exception)}{\ttindex{KeyboardInterrupt}}
306306
\exception{KeyboardInterrupt} will be raised. It may be called
307307
without holding the interpreter lock.
308+
% XXX This was described as obsolete, but is used in
309+
% thread.interrupt_main() (used from IDLE), so it's still needed.
308310
\end{cfuncdesc}
309311

310312
\begin{cfuncdesc}{PyObject*}{PyErr_NewException}{char *name,

0 commit comments

Comments
 (0)