New submission from Benjamin Ryzman <benjamin+pyt...@ryzman.fr>: http://pastie.org/1025197
Is it deemed acceptable that setting up one's own SIGCHLD handler breaks communicate()? I did not find it in the documentation. With the above workaround one can mix communicate() processes with processes spawned in the background that one's too lazy to wait for. ---------- messages: 108990 nosy: zarkdav priority: normal severity: normal status: open title: subprocess.Popen.communicate() and SIGCHLD handlers type: feature request versions: Python 2.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9127> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
