New submission from Brandon Craig Rhodes <bran...@rhodesmill.org>: Normally, unittest cleanly reports an exception in a setUpClass method. But if I place the attached test in a directory by itself and then run "python -m unittest discover -b" from inside of the same directory, then instead of being shown the setUpClass exception I am instead shown a long traceback because unittest seems to think that it has put a stringIO in place of sys.stdout but a file is there instead.
---------- components: Library (Lib) files: test_example.py messages: 126816 nosy: brandon-rhodes priority: normal severity: normal status: open title: setUpClass exception causes explosion with "-b" type: crash versions: Python 2.7 Added file: http://bugs.python.org/file20484/test_example.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10979> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
