Exit from a Python function during exception unwinding. This includes exceptions raised directly within the

function and that are allowed to continue to propagate.

:monitoring-event:`STOP_ITERATION` can be locally disabled, unlike

:monitoring-event:`RAISE`.

Note that the :monitoring-event:`STOP_ITERATION` event and the

:monitoring-event:`RAISE` event for a :exc:`StopIteration` exception are

equivalent, and are treated as interchangeable when generating events.

Implementations will favor :monitoring-event:`STOP_ITERATION` for performance

reasons, but may generate a :monitoring-event:`RAISE` event with a

:exc:`StopIteration`.

must be registered. Events can be turned on or off by setting the events either

even if it is turned on both globally and locally.

Callbacks are called only once regardless if the event is turned on both

globally and locally. As such, if an event could be turned on for both global

and local events by your code then the callback needs to be written to handle

either trigger.

Callback functions returning an object other than :data:`DISABLE` will have no effect.

* :monitoring-event:`CALL`, :monitoring-event:`C_RAISE` and :monitoring-event:`C_RETURN`

(*arg0* can be :data:`MISSING` specifically)::

*code* represents the code object where the call is being made, while

*callable* is the object that is about to be called (and thus

triggered the event).

For instance methods, *callable* will be the function object as found on the

class with *arg0* set to the instance (i.e. the ``self`` argument to the

method).