[Python-Dev] lltrace (original) (raw)
Guido van Rossum guido at python.org
Sat Apr 14 16:58:01 CEST 2007
- Previous message: [Python-Dev] __lltrace__
- Next message: [Python-Dev] Making builtins more efficient
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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/testtrace.py, lines 609 onwards: def test16nojumpintofinallyblock(self): globals()["lltrace"] = 1 self.runtest(nojumpintofinallyblock) 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/)
- Previous message: [Python-Dev] __lltrace__
- Next message: [Python-Dev] Making builtins more efficient
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]