[Python-Dev] Last chance!
tismer at tismer.com
Fri Dec 19 12:49:15 EST 2003
Guido van Rossum wrote:
> I saved the message, but haven't had the time yet to think things
> I *did* notice at least one case where using f_tstate might actually
> be a mistake: theoretically it's possible that two or more threads
> alternate calling next() on a generator (if they wrap it in a critical
> section); AFAICT the f_tstate is never updated.
Right, f_tstate is never updated.
I think there is another inconsistent
situation, which can be created easily.
If a generator is run by a different thread
than it's creator, then the frame is run in that
other thread. eval_fame correctly uses tstate,
but if tracing is activated, call_trace uses
frame->f_tstate for no obvious reason, which
will probably mess up the tracing flags of the wrong
ciao - chris
Christian Tismer :^) <mailto:tismer at tismer.com>
Mission Impossible 5oftware : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34 home +49 30 802 86 56 mobile +49 173 24 18 776
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
More information about the Python-Dev