This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients berker.peksag, demian.brecht, ezio.melotti, michael.foord, pitrou, r.david.murray, rbcollins, serhiy.storchaka, zach.ware
Date 2014-09-26.15:35:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1411745702.17.0.945543928309.issue22197@psf.upfronthosting.co.za>
In-reply-to
Content
> 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).
History
Date User Action Args
2014-09-26 15:35:02ezio.melottisetrecipients: + ezio.melotti, pitrou, rbcollins, r.david.murray, michael.foord, berker.peksag, zach.ware, serhiy.storchaka, demian.brecht
2014-09-26 15:35:02ezio.melottisetmessageid: <1411745702.17.0.945543928309.issue22197@psf.upfronthosting.co.za>
2014-09-26 15:35:02ezio.melottilinkissue22197 messages
2014-09-26 15:35:02ezio.melotticreate