[issue4216] subprocess.Popen hangs at communicate() when child exits

Terry J. Reedy added the comment: Closing as suggested by Ross -- nosy: +terry.reedy resolution: -> rejected status: open -> closed versions: +Python 3.3 -Python 2.7, Python 3.1 ___ Python tracker

[issue4216] subprocess.Popen hangs at communicate() when child exits

Arty added the comment: You can try subprocess.call() with close_fds=True. It helped me, at least. -- nosy: +elmysnail ___ Python tracker ___

[issue4216] subprocess.Popen hangs at communicate() when child exits

Ross Lagerwall added the comment: Yes I think subprocess is working correctly. Since this feature request is 2 years old now without any interest, I think it should be closed. If the functionality is needed, it can always be programmed by the user when needed. -- nosy: +rosslagerwall

[issue4216] subprocess.Popen hangs at communicate() when child exits

Changes by Dave Malcolm : -- nosy: +dmalcolm ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue4216] subprocess.Popen hangs at communicate() when child exits

Changes by STINNER Victor : -- nosy: -haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue4216] subprocess.Popen hangs at communicate() when child exits

Gabriel Genellina added the comment: I think communicate() works as documented now: reads stdout/stderr until EOF, *and* waits for subprocess to terminate. You're asking for a different method, or perhaps an optional parameter "return_when_died" to communicate, so it returns as soon as the c

[issue4216] subprocess.Popen hangs at communicate() when child exits

Louis-Dominique Dubeau <[EMAIL PROTECTED]> added the comment: I'm running python 2.5.2 on Ubuntu 8.10. I believe I've also encountered the problem reported here. The scenario in my case was the following: 1. Python process A uses subprocess.Popen to create another python process (B). Process

[issue4216] subprocess.Popen hangs at communicate() when child exits

STINNER Victor <[EMAIL PROTECTED]> added the comment: The bug should be fixed in Python 2.5 since it uses: while read_set or write_set: try: rlist, wlist, xlist = select.select(read_set, write_set, []) except select.error, e: if e[0] == errno.EINTR:

[issue4216] subprocess.Popen hangs at communicate() when child exits

Amy <[EMAIL PROTECTED]> added the comment: Yes, I can only replicate this issue with command to start firewall. Stopping firewall or other service commands don't have the problem. Check Point firewall is a kernel application. Somehow select system call is interrupted and can't terminate the PIP

[issue4216] subprocess.Popen hangs at communicate() when child exits

STINNER Victor <[EMAIL PROTECTED]> added the comment: I'm unable to reproduce your problem with Python 2.4.4 nor Python 2.5.1. I'm using Ubuntu and the program "service" doesn't exist. So I used the commands "pwd", "sh -c pwd", "sh -c 'echo $$'". All commands terminate correctly. Your problem

[issue4216] subprocess.Popen hangs at communicate() when child exits

Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: -- nosy: +belopolsky ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-lis

[issue4216] subprocess.Popen hangs at communicate() when child exits

New submission from Amy <[EMAIL PROTECTED]>: I have a simple program to call a shell command "service cpboot start" to start Check Point firewall on RHEL5.1. = #!/usr/bin/env python # vim: softtabstop=4 shiftwidth=4 expandtab import os from subprocess import * p = Popen('servic