[Stackless] [bug] frame.f_back is frame

Christopher Armstrong radix at twistedmatrix.com
Sun Jan 18 00:13:22 CET 2004

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?

  Twisted | Christopher Armstrong: International Man of Twistery
   Radix  |          Release Manager,  Twisted Project
---------+           http://radix.twistedmatrix.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
URL: <http://www.stackless.com/pipermail/stackless/attachments/20040117/85d4c108/attachment.pgp>
-------------- next part --------------
Stackless mailing list
Stackless at stackless.com

More information about the Stackless mailing list