[New-bugs-announce] [issue47046] Add `f_state` attribute to FrameObjects.

[Mark Shannon]

New submission from Mark Shannon <mark at hotpy.org>:

When tracing, the event supplied is insufficient to determine what is actually happening.

E.g. A "call" event could be a call to a function or resuming a generator or coroutine.

Adding a state field to the FrameObject would allow these cases to be disambiguated without having to make dubious deductions from `f_lasti` or other frame attributes.

The proposed states would be:

FRAME_CREATED    # Frame created, but not executed at all
FRAME_SUSPENDED  # Frame suspended after yield or yield from
FRAME_EXECUTING  # Frame is executed normally
FRAME_COMPLETED  # Frame has completed 
FRAME_CLEARED    # Frame has been cleared


Ned, any other states that you might need to know about?

----------
messages: 415427
nosy: Mark.Shannon, nedbat
priority: normal
severity: normal
status: open
title: Add `f_state` attribute to FrameObjects.

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue47046>
_______________________________________