
Hello again. So, using __lltrace__, I stumbled over a crashbug (to which I have already submitted a fix).i To trigger the crash, I modified lib/test/test_trace.py, lines 609 onwards: def test_16_no_jump_into_finally_block(self): globals()["__lltrace__"] = 1 self.run_test(no_jump_into_finally_block) del globals()["__lltrace__"] This would crash in all versions I tried. Now, I wonder, is it worth it adding a regression test for the __lltrace__ functionality? I realize it is a debug feature, only availible in debug builds, for debugging python itself, on the other hand, it had been broken for a long time and no one had noticed, hence perhaps the need for a test? What do you think? Kristján

The __lltrace__ feature costs in maintenance; it should either be fixed or ripped out. On 4/14/07, Kristján Valur Jónsson <kristjan@ccpgames.com> wrote:
-- --Guido van Rossum (home page: http://www.python.org/~guido/)

The __lltrace__ feature costs in maintenance; it should either be fixed or ripped out. On 4/14/07, Kristján Valur Jónsson <kristjan@ccpgames.com> wrote:
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
participants (2)
-
Guido van Rossum
-
Kristján Valur Jónsson