Lines Matching refs:indicator

13 there is a global indicator (per thread) of the last error that occurred.  Most
15 the error on failure.  Most functions also return an error indicator, usually
21 doesn't set the error indicator; the function it called already set it.  It is
35 The error indicator consists of three Python objects corresponding to   the
37 API functions exist to interact with the error indicator in various ways.  There
38 is a separate error indicator for each thread.
46    Print a standard traceback to ``sys.stderr`` and clear the error indicator.
47    Call this function only when the error indicator is set.  (Otherwise it will
62    Test whether the error indicator is set.  If set, return the exception *type*
102    Clear the error indicator.  If the error indicator is not set, there is no
108    Retrieve the error indicator into three variables whose addresses are passed.
109    If the error indicator is not set, set all three variables to *NULL*.  If it is
116       by code that needs to save and restore the error indicator temporarily.
121    Set  the error indicator from the three objects.  If the error indicator is
123    indicator is cleared.  Do not pass a *NULL* type and non-*NULL* value or
134       error indicator temporarily; use :c:func:`PyErr_Fetch` to save the current
140    This is the most common way to set the error indicator.  The first argument
154    This function sets the error indicator and returns *NULL*.  *exception*
189    this calls :c:func:`PyErr_CheckSignals`, and if that set the error indicator,
344    exception is raised the error indicator is set and the function returns ``-1``;
345    otherwise the function returns ``0``.  The error indicator may or may not be