Steve Dower <steve.do...@python.org> added the comment:
Thanks for spotting this! There's no "rationale" for hiding the output - what happened is I streamlined the test suite to always capture output, instead of some tests deciding whether they ought to capture it or not (and some doing incredibly weird things when capturing, and others capturing the capture). While I was testing I went immediately to `print(file=sys.__stderr__)`, since that's what I normally do, but it shouldn't be too hard to make the test suite only capture output when collecting it for the test results. I'll try and get to it in the next two weeks, depending on how my conference schedules work out. I'm also happy to review someone else's change. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue34945> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
