Title: subprocess.communicate with timeout 0 and already terminated process generates TimeoutExpired on Linux
Type: behavior Stage:
Components: Library (Lib) Versions: Python 3.6
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Griffon26, spoorcc
Priority: normal Keywords:

Created on 2017-02-07 11:57 by Griffon26, last changed 2017-02-07 12:36 by spoorcc.

File name Uploaded Description Edit Griffon26, 2017-02-07 11:58 A minimal example that shows the problem
Messages (1)
msg287230 - (view) Author: Maurice van der Pot (Griffon26) Date: 2017-02-07 11:57
This only happens when:
- timeout is small enough
- at least one stream is redirected to a PIPE

When I know for certain that a subprocess has already terminated and I call communicate to retrieve its results with a timeout of 0 (or other small enough value), communicate will always return TimeoutExpired.

The cause is that the check on timeout is done before the ready file descriptors are checked: With a small enough timeout, communicate will never check the file descriptors for EOF.

From a user perspective I would expect to be able to use communicate(timeout=0) to get the output for a process that I know has already terminated or to poll without blocking.

Is this the intended behaviour of communicate or is it a bug? To me this behaviour is surprising.
Date User Action Args
2017-02-07 12:36:53spoorccsetnosy: + spoorcc
2017-02-07 11:58:21Griffon26setfiles: +
2017-02-07 11:57:14Griffon26create