[issue4034] traceback attribute error

STINNER Victor added the comment: @benjamin.peterson: Cool! Thanks. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue4034] traceback attribute error

Benjamin Peterson added the comment: Fixed in r70463. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Pytho

[issue4034] traceback attribute error

STINNER Victor added the comment: Ping. benjamin.peterson's patch fixes the very strange issue, and I would like to see it upstream. About clearing the frame/traceback, it's another issue (#1565525). -- ___ Python tracker

[issue4034] traceback attribute error

Antoine Pitrou added the comment: One possibility would be to only allow deleting the tb_frame attribute (setting it to NULL), not setting it to an arbitrary object. -- nosy: +pitrou ___ Python tracker

[issue4034] traceback attribute error

Changes by STINNER Victor <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11719/traceback_tb_frame_setter.patch ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue4034] traceback attribute error

STINNER Victor <[EMAIL PROTECTED]> added the comment: My patch causes a crash with: import sys try: raise Exception("hm!") except: t, v, tb = sys.exc_info() tb.tb_frame = {} raise t, v, tb Change tb.tb_frame value is not a good idea. It's better to clear locals/globals: see msg

[issue4034] traceback attribute error

STINNER Victor <[EMAIL PROTECTED]> added the comment: Instead of converting tb_frame attribute to read only, I prefer to allow the user to clear the traceback to free some memory bytes. So I wrote a different patch. marge$ ./python Python 2.7a0 (trunk:66786M, Oct 7 2008, 00:48:32) >>> try: ..

[issue4034] traceback attribute error

Greg Hazel <[EMAIL PROTECTED]> added the comment: There seem to be some other exception type and string inconsistencies, but they are not new to Python 2.6 >>> tb.tb_frame = None Traceback (most recent call last): File "", line 1, in TypeError: 'traceback' object has only read-only attribute

[issue4034] traceback attribute error

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Here's a patch. It looks like traceback just needs to use a struct sequence instead of providing tp_getattr its self. -- keywords: +needs review, patch nosy: +benjamin.peterson Added file: http://bugs.python.org/file11703/use_struc

[issue4034] traceback attribute error

New submission from Greg Hazel <[EMAIL PROTECTED]>: Unrelated to this bug, I would like to have the ability to remove the reference to the frame from the traceback object. Specifically so that the traceback object could be stored for a while without keeping all the locals alive as well. So, p