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 sbt
Recipients Andrew.Boettcher, BreamoreBoy, ajaksu2, astrand, cvrebert, ericpruitt, giampaolo.rodola, josiahcarlson, ooooooooo, parameter, r.david.murray, rosslagerwall, sbt, techtonik
Date 2012-05-23.13:52:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337781130.18.0.882230425073.issue1191964@psf.upfronthosting.co.za>
In-reply-to
Content
> How would this differ from the normal communicate()?

It would block until one of the following occurs:

* some data has been written to stdin,
* some data has been read from stdout or stderr, or
* timeout passes (if timeout is not None).

The normal communicate() could be implemented by running this in a loop.  The amount of data returned at once could be limited by an argument of the constructor.
History
Date User Action Args
2012-05-23 13:52:10sbtsetrecipients: + sbt, josiahcarlson, astrand, parameter, techtonik, giampaolo.rodola, ajaksu2, ooooooooo, r.david.murray, cvrebert, ericpruitt, BreamoreBoy, Andrew.Boettcher, rosslagerwall
2012-05-23 13:52:10sbtsetmessageid: <1337781130.18.0.882230425073.issue1191964@psf.upfronthosting.co.za>
2012-05-23 13:52:09sbtlinkissue1191964 messages
2012-05-23 13:52:09sbtcreate