Mercurial > cpython-lru_cache-weakref
diff Doc/api/init.tex @ 20460:ffbf94fd9cef legacy-trunk
Update the description of PyTrace_EXCEPT.
| author | Fred Drake <fdrake@acm.org> |
|---|---|
| date | Tue, 16 Oct 2001 19:23:55 +0000 |
| parents | 946bebd00132 |
| children | 82a8ca3c928c a5eeb288e020 |
line wrap: on
line diff
--- a/Doc/api/init.tex Tue Oct 16 19:22:51 2001 +0000 +++ b/Doc/api/init.tex Tue Oct 16 19:23:55 2001 +0000 @@ -708,11 +708,14 @@ \begin{cvardesc}{int}{PyTrace_EXCEPT} The value of the \var{what} parameter to a \ctype{Py_tracefunc} - function when an exception has been raised by Python code as the - result of an operation. The operation may have explictly intended - to raise the operation (as with a \keyword{raise} statement), or may - have triggered an exception in the runtime as a result of the - specific operation. + function when an exception has been raised. The callback function + is called with this value for \var{what} when after any bytecode is + processed after which the exception becomes set within the frame + being executed. The effect of this is that as exception propogation + causes the Python stack to unwind, the callback is called upon + return to each frame as the exception propogates. Only trace + functions receives these events; they are not needed by the + profiler. \end{cvardesc} \begin{cvardesc}{int}{PyTrace_LINE}
