Message415427
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? |
|
Date |
User |
Action |
Args |
2022-03-17 16:40:39 | Mark.Shannon | set | recipients:
+ Mark.Shannon, nedbat |
2022-03-17 16:40:39 | Mark.Shannon | set | messageid: <1647535239.19.0.523349265892.issue47046@roundup.psfhosted.org> |
2022-03-17 16:40:39 | Mark.Shannon | link | issue47046 messages |
2022-03-17 16:40:39 | Mark.Shannon | create | |
|