➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients ncoghlan, pitrou
Date 2010-10-28.13:05:08
SpamBayes Score 7.7893304e-08
Marked as misclassified No
Message-id <AANLkTinq_L813DY680ho9t+2sfdX9bCvZvKqd46zqbg1@mail.gmail.com>
In-reply-to <1288270513.75.0.411536303265.issue10220@psf.upfronthosting.co.za>
Content 
On Thu, Oct 28, 2010 at 10:55 PM, Antoine Pitrou <report@bugs.python.org> wrote:
>
> Antoine Pitrou <pitrou@free.fr> added the comment:
>
> Is it CPython-specific?

The states are not CPython-specific (they're logical states of the
underlying generator), but I don't know if other implementations
expose generator and frame details in the same way (all the more
reason to put this in inspect - other implementations can provide the
information without needing to exactly mimic gi_frame and f_lasti).

> Does "currently executing" also include "currently closing"?

"Currently executing" means the frame is being evaluated in a Python
thread (the thread running it may be suspended in a multi-threaded
environment, but the frame itself is in the middle of doing something,
which may include processing a thrown in GeneratorExit)
History
Date User Action Args
2010-10-28 13:05:10ncoghlansetrecipients: + ncoghlan, pitrou
2010-10-28 13:05:09ncoghlanlinkissue10220 messages
2010-10-28 13:05:08ncoghlancreate