[issue14872] subprocess is not safe from deadlocks
Richard Oudkerk
report at bugs.python.org
Tue May 22 00:24:09 CEST 2012
Richard Oudkerk <shibturn at gmail.com> added the comment:
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;-)
----------
nosy: +sbt
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14872>
_______________________________________
More information about the Python-bugs-list
mailing list