Nick Bastin wrote:
On Mar 29, 2004, at 10:23 AM, Guido van Rossum wrote:
Since the profiler is being invoked from the thread being profiled, how could it end up not being in the same thread?
(If I am missing something, I must be missing a *lot* about your design, so you might want to say quite a bit more on how it works.)
...previous reply to this email deleted after some testing...
Nevermind, the specific situation that I was concerned about actually can't occur. I wasn't sure that I could make a guarantee that the profiler would be invoked from the same thread as the code being profiled in all cases of thread destruction, but that appears to be an unwarranted concern.
You are the first person since months who claimed a possible use of f_tstate. Please make sure that you really don't need it. It needs to be changed, anyway: Either it must be updated for generators for every run, or it should be dropped. cheers - chris -- Christian Tismer :^) <mailto:tismer@stackless.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/