[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers

Gregory P. Smith added the comment: fixed via http://hg.python.org/cpython/rev/767420808a62 -- dependencies: +race condition in subprocess module nosy: +gregory.p.smith ___ Python tracker __

[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers

Ned Deily added the comment: Thanks for the problem report. And thanks for noticing the fix. -- nosy: +ned.deily resolution: -> out of date stage: -> committed/rejected status: open -> closed versions: +Python 2.7 ___ Python tracker

[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers

Ross Lagerwall added the comment: This has been fixed in 2.7 and 3.2 so I think that this issue can be closed. -- nosy: +rosslagerwall ___ Python tracker ___

[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers

Terry J. Reedy added the comment: Can you suggest a specific doc patch with new text and location? -- nosy: +terry.reedy versions: +Python 3.2 -Python 2.6 ___ Python tracker ___

[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers

Benjamin Ryzman added the comment: Content of the above pastie: Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56) [GCC 4.4.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import signal >>> import subprocess >>> signal.signal(signal.SIGCHLD,signal.SIG_IGN)

[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers

Jean-Paul Calderone added the comment: You should include all relevant issue materials here, in the Python issue tracker. This ticket will be useless as soon as pastie.org decides to forget about your paste. -- nosy: +exarkun ___ Python tracker <

[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers

Changes by Benjamin Ryzman : -- assignee: -> d...@python components: +Documentation, Library (Lib) nosy: +d...@python ___ Python tracker ___ _

[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers

New submission from Benjamin Ryzman : 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 backgrou