[Python-Dev] __lltrace__

[Guido van Rossum]

The __lltrace__ feature costs in maintenance; it should either be
fixed or ripped out.

On 4/14/07, Kristján Valur Jónsson <kristjan at ccpgames.com> wrote:
>
>
>
>
> 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
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> http://mail.python.org/mailman/options/python-dev/guido%40python.org
>
>


-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)