mirror of
https://github.com/python/cpython.git
synced 2025-11-02 19:12:55 +00:00
Update the description of PyTrace_EXCEPT.
This commit is contained in:
parent
ab9b238ced
commit
5bf1ecd503
1 changed files with 8 additions and 5 deletions
|
|
@ -708,11 +708,14 @@ previous versions.
|
||||||
|
|
||||||
\begin{cvardesc}{int}{PyTrace_EXCEPT}
|
\begin{cvardesc}{int}{PyTrace_EXCEPT}
|
||||||
The value of the \var{what} parameter to a \ctype{Py_tracefunc}
|
The value of the \var{what} parameter to a \ctype{Py_tracefunc}
|
||||||
function when an exception has been raised by Python code as the
|
function when an exception has been raised. The callback function
|
||||||
result of an operation. The operation may have explictly intended
|
is called with this value for \var{what} when after any bytecode is
|
||||||
to raise the operation (as with a \keyword{raise} statement), or may
|
processed after which the exception becomes set within the frame
|
||||||
have triggered an exception in the runtime as a result of the
|
being executed. The effect of this is that as exception propogation
|
||||||
specific operation.
|
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}
|
\end{cvardesc}
|
||||||
|
|
||||||
\begin{cvardesc}{int}{PyTrace_LINE}
|
\begin{cvardesc}{int}{PyTrace_LINE}
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue