Message227626
> As for output buffering, may be replace sys.stdout by file-like object
> which flushes its buffered content to original stdout on failure and
> discard it on success.
This is what the --buffer option is already supposed to do (I only found out about it thanks to this issue, the name is not very indicative of what it does...). IIUC what Antoine is suggesting is having a more fine-grained control of the buffering, and the ability to set it from individual test cases rather than using a global command line flag or unittest.main(buffer=True) (which is only used while executing the test file directly). |
|
Date |
User |
Action |
Args |
2014-09-26 15:35:02 | ezio.melotti | set | recipients:
+ ezio.melotti, pitrou, rbcollins, r.david.murray, michael.foord, berker.peksag, zach.ware, serhiy.storchaka, demian.brecht |
2014-09-26 15:35:02 | ezio.melotti | set | messageid: <1411745702.17.0.945543928309.issue22197@psf.upfronthosting.co.za> |
2014-09-26 15:35:02 | ezio.melotti | link | issue22197 messages |
2014-09-26 15:35:02 | ezio.melotti | create | |
|