Lines Matching refs:indicator

13 there is a global indicator (per thread) of the last error that occurred.  Most
16 indicator, usually ``NULL`` if they are supposed to return a pointer, or ``-1``
20 Concretely, the error indicator consists of three object pointers: the
27 doesn't set the error indicator; the function it called already set it.  It is
37    The error indicator is **not** the result of :func:`sys.exc_info()`.
49    Clear the error indicator.  If the error indicator is not set, there is no
55    Print a standard traceback to ``sys.stderr`` and clear the error indicator.
60    Call this function **only** when the error indicator is set.  Otherwise it
93 These functions help you set the current thread's error indicator.
100    This is the most common way to set the error indicator.  The first argument
114    This function sets the error indicator and returns ``NULL``.  *exception*
158    this calls :c:func:`PyErr_CheckSignals`, and if that set the error indicator,
366 Querying the error indicator
371    Test whether the error indicator is set.  If set, return the exception *type*
402    Retrieve the error indicator into three variables whose addresses are passed.
403    If the error indicator is not set, set all three variables to ``NULL``.  If it is
410       by code that needs to save and restore the error indicator temporarily, e.g.::
424    Set  the error indicator from the three objects.  If the error indicator is
426    indicator is cleared.  Do not pass a ``NULL`` type and non-``NULL`` value or
437       error indicator temporarily.  Use :c:func:`PyErr_Fetch` to save the current
438       error indicator.
511    exception is raised the error indicator is set and the function returns ``-1``;
512    otherwise the function returns ``0``.  The error indicator may or may not be