➜

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 r.david.murray
Recipients brett.cannon, ezio.melotti, flox, georg.brandl, michael.foord, r.david.murray, tarek, tim.golden
Date 2010-04-16.19:10:16
SpamBayes Score 0.00038444513
Marked as misclassified No
Message-id <1271445017.9.0.405984076307.issue8273@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm writing unittests for a program I'm writing, and would really love to be able to use captured_stdout/stderr.  Of course, I have to support Python 2.5, and can't really justify installing unittest2, so I'll have to roll my own anyway, but I'm definitely +1 for those functions to move into unittest.  A bunch of the others, too, but that's the one I just looked at, and the API looks good to me.  (I'd rename captured_output and leave it be an implementation detail.)

How about 'tools' for the submodule name?
History
Date User Action Args
2010-04-16 19:10:18r.david.murraysetrecipients: + r.david.murray, brett.cannon, georg.brandl, tim.golden, tarek, ezio.melotti, michael.foord, flox
2010-04-16 19:10:17r.david.murraysetmessageid: <1271445017.9.0.405984076307.issue8273@psf.upfronthosting.co.za>
2010-04-16 19:10:16r.david.murraylinkissue8273 messages
2010-04-16 19:10:16r.david.murraycreate