[issue2475] Popen.poll always returns None

Changes by David Andrzejewski : -- nosy: +dandrzejewski ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue2475] Popen.poll always returns None

Changes by Terry J. Reedy : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue2475] Popen.poll always returns None

Mike Lisanke added the comment: Terry, I had long since coded around the problem. At this point, I no longer have the test environment to cause the intermittent conditions of the process hang. I could code something up, but; your question is the first response to this bug report since "reiko "

[issue2475] Popen.poll always returns None

Terry J. Reedy added the comment: Should this be closed or is this still a problem in 2.7 (release candidate out now, final soon) or 3.1? -- nosy: +tjreedy ___ Python tracker __

[issue2475] Popen.poll always returns None

reiko <[EMAIL PROTECTED]> added the comment: I have also run into this problem. If you only use p.poll() and never p.wait(), returncode will always remain None. roudkerk's workaround doesn't seem to work with the new Popen objects, at least in python 2.4. ("unexpected keyword argument '_deadst

[issue2475] Popen.poll always returns None

Mike Lisanke <[EMAIL PROTECTED]> added the comment: Isn't this a critical problem. The .poll() function serves as a means to check the status of the process started. When it continues to report 'None' to a process which has already terminated, it creates a false positive of a hung process. Dealin

[issue2475] Popen.poll always returns None

Josh Cogliati <[EMAIL PROTECTED]> added the comment: Hm. Well, after filing the bug, I created a thread for each subprocess, and had that thread do an wait on the process, and that worked fine. So, I guess at minimum it sounds like the documentation for poll could be improved to mention that it

[issue2475] Popen.poll always returns None

roudkerk <[EMAIL PROTECTED]> added the comment: The problem is that os.wait() does not play nicely with subprocess.py. Popen.poll() and Popen.wait() use os.waitpid(pid, ...) which will raise OSError if pid has already been reported by os.wait(). Popen.poll() swallows OSError and by default retur

[issue2475] Popen.poll always returns None

New submission from Josh Cogliati <[EMAIL PROTECTED]>: I was trying to use subprocess to run multiple processes, and then wait until one was finished. I was using poll() to do this and created the following test case: #BEGIN import subprocess,os procs = [subprocess.Popen(["sleep",str(x)]) for x