At 06:24 PM 9/3/2005 +1000, Christopher Armstrong wrote: >For example, perhaps a better idea would be to >change the traceback-printing functions to use Python attribute lookup >instead of internal structure lookup, and then change raise to accept >arbitrary Python objects as its third argument, as long as it matches >the traceback interface.
Given that traceback printing isn't a performance-critical activity, there probably isn't a reason any more for requiring a particular C layout. On the other hand, being able to create frame or traceback instances or subclasses would probably also solve your problem, without having to do too much hacking on the C code that expects a particular layout. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
