Message126816
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. |
|
Date |
User |
Action |
Args |
2011-01-22 04:13:32 | brandon-rhodes | set | recipients:
+ brandon-rhodes |
2011-01-22 04:13:31 | brandon-rhodes | set | messageid: <1295669611.84.0.453494131357.issue10979@psf.upfronthosting.co.za> |
2011-01-22 04:13:29 | brandon-rhodes | link | issue10979 messages |
2011-01-22 04:13:28 | brandon-rhodes | create | |
|