[Python-Dev] unittest output

Raymond Hettinger python at rcn.com
Wed Dec 3 05:02:03 EST 2003

> > 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.
> http://www.python.org/sf/722638

Arghh.  I had forgotten that Steve Purcell weighed in on this.
It's his module.  So unless he can be persuaded, the point is moot :-(

> > So, I would like to re-raise the issue.
> > Can we get this fixed?
> Yes, please.

Raymond Hettinger

More information about the Python-Dev mailing list