Message 161303 - Python tracker

➜

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	sbt, techtonik
Date	2012-05-21.22:24:08
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1337639049.0.0.10063490584.issue14872@psf.upfronthosting.co.za>
In-reply-to

Content
I think the note for communicate() just means that you might get MemoryError (or some other exception) if the output is too big. But I agree it is ambiguous. communicate() uses select() on Unix and threads on Windows, so deadlocks should not be possible. > So, what should I use? Use communicate() (on a machine with infinite memory;-)

I think the note for communicate() just means that you might get MemoryError (or some other exception) if the output is too big.  But I agree it is ambiguous.

communicate() uses select() on Unix and threads on Windows, so deadlocks should not be possible.

> So, what should I use?

Use communicate() (on a machine with infinite memory;-)

History
Date	User	Action	Args
2012-05-21 22:24:09	sbt	set	recipients: + sbt, techtonik
2012-05-21 22:24:09	sbt	set	messageid: <1337639049.0.0.10063490584.issue14872@psf.upfronthosting.co.za>
2012-05-21 22:24:08	sbt	link	issue14872 messages
2012-05-21 22:24:08	sbt	create