Kaydet (Commit) 5bf1ecd5 authored tarafından Fred Drake's avatar Fred Drake

Update the description of PyTrace_EXCEPT.

üst ab9b238c
...@@ -708,11 +708,14 @@ previous versions. ...@@ -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}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment