A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2007-April/072608.html below:

[Python-Dev] __lltrace__

[Python-Dev] __lltrace__Kristján Valur Jónsson kristjan at ccpgames.com
Sat Apr 14 11:14:08 CEST 2007
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20070414/9a05c088/attachment.htm 
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4