[issue16164] there is no easy way to force unittest.main to use stdout rather than stderr

2012-10-09 Thread Michael Foord
Michael Foord added the comment: Unfortunately subclassing core components is the *intended* mechanism for customising unittest behaviour. Changing this is possible, but is a big job with very extensive changes. I don't think this request is *invalid* per-se, but it isn't something that

[issue16164] there is no easy way to force unittest.main to use stdout rather than stderr

2012-10-08 Thread Alexander Belchenko
New submission from Alexander Belchenko: Why by default unittest.main (which uses unittest.TextTestRunner) prints everything to stderr. What the reason behind this behavior? It makes very inconvenient to run big test suite with less, i.e. python test.py | less or python test.py test.log

[issue16164] there is no easy way to force unittest.main to use stdout rather than stderr

2012-10-08 Thread R. David Murray
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

[issue16164] there is no easy way to force unittest.main to use stdout rather than stderr

2012-10-08 Thread R. David Murray
R. David Murray added the comment: I'm pretty sure this should be closed as won't fix or invalid, but I'll leave that to Michael, who is the current maintainer of unittest. -- nosy: +michael.foord ___ Python tracker rep...@bugs.python.org