[issue2475] Popen.poll always returns None

[Mike Lisanke]

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. Dealing with recovery from an actual hung
process is difficult enough. Having to deal with a bad detection that
the process ran to completion on top of this, makes the use of
subprocess difficult. 

Maybe I'm miss applying the .poll() function. I'm trying to detect that
a process has hung, prior to calling .stdout.readlines(). The
readlines() will hang my python script if the process is hung. Is there
another way I should be doing this?

Thanks, 

Mike

--
nosy: +lisanke

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2475>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2475] Popen.poll always returns None

[Mike Lisanke]

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 " on 7/28/2008. I
suggest it can be closed, and would be reopened when encountered again. I
appears nobody is working in that area of code.

On Wed, Jun 16, 2010 at 8:13 PM, Terry J. Reedy wrote:

>
> 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 
> <http://bugs.python.org/issue2475>
> ___
>

--
Added file: http://bugs.python.org/file17719/unnamed

___
Python tracker 
<http://bugs.python.org/issue2475>
___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 <mailto:j.k.langri...@gmail.com"; style="color: rgb(17, 65, 112); 
">j.k.langri...@gmail.com>" on 7/28/2008. I suggest it can be 
closed, and would be reopened when encountered again. I appears nobody is 
working in that area of code. 

On Wed, Jun 16, 2010 at 8:13 PM, Terry J. Reedy 
<mailto:rep...@bugs.python.org";>rep...@bugs.python.org> 
wrote:


Terry J. Reedy <mailto:tjre...@udel.edu";>tjre...@udel.edu> 
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 <mailto:rep...@bugs.python.org";>rep...@bugs.python.org>
<http://bugs.python.org/issue2475"; 
target="_blank">http://bugs.python.org/issue2475>
___
-- Best 
regards,Mike

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com