[Stackless] [bug] frame.f_back is frame
tismer at stackless.com
Sun Jan 18 05:03:21 CET 2004
Christopher Armstrong wrote:
> Twisted's twisted.python.failure.Failure object does a lot of
> introspecting with frames. It walks back the stack with the f_back
> attribute of frame objects. In regular Python, this eventually
> terminates with f_back being None, but apparently stackless's baseframe
> object is "terminating" it by pointing f.f_back at itself, so creating a
> Failure object is going in an infinite loop while Failure waits for
> f_back to be None.
> Any chance of getting this fixed?
Oh, this was sort-of a shortcut to make certain things eqasier.
But if Twisted dislikes it, I will try to revert that.
ciao - chris
Christian Tismer :^) <mailto:tismer at 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/
Stackless mailing list
Stackless at stackless.com
More information about the Stackless