[Python-Dev] unittest output (original) (raw)
Raymond Hettinger raymond.hettinger at verizon.net
Wed Dec 3 04:21:32 EST 2003
- Previous message: [Python-Dev] Tutorial: Brief Introduction to the Standard Libary
- Next message: [Python-Dev] unittest output
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
When a test fails, it is accompanied by tracebacks that include all the processing within the unittest module itself. This makes it darned difficult to see at a glance what went wrong. If like me, you use unittest as part of the development process, then you run it hundreds of times each week and this eyesore gets to be a real PITA.
I don't recall when or where, but someone has proposed a fix. But, like many great ideas, it got stymied because someone, somewhere has a use for the rest of the traceback. Also, a developer raised the (IMO red herring) issue -- what if there is a bug in the unittest module, how would you track it.
So, I would like to re-raise the issue. Can we get this fixed?
One other nit: When unittest.main() is run from the new IDLE it fails on a sys.exit() attempt. Can we trap the exit, and just return?
Raymond Hettinger
- Previous message: [Python-Dev] Tutorial: Brief Introduction to the Standard Libary
- Next message: [Python-Dev] unittest output
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]