R. David Murray added the comment: I think the reason is that this enables you to easily see if the tests generate any output to stdout. This was important when unittest was introduced into python, because some of our tests at that time were still written to check the stdout output against "known good" output, and in the process of converting them we would make sure that stdout was empty after the unittest run. Those tests have all been converted a fairly long time ago now.
It is an interesting question whether this decision could be revisited. The problem is that there may well be other people depending on the current behavior, which many people may view as the correct behavior. I myself am neutral on the question, though I have experienced the annoyance of having to run unittest twice when I forget that the output goes to stderr...the second time to do the equivalent of 'python test.py 2>&1 | less'. ---------- nosy: +r.david.murray _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16164> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
