[issue23288] subprocess.Popen close_fds behaviour differs between 3.2 and 3.4

Changes by R. David Murray : -- resolution: -> not a bug stage: -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue23288] subprocess.Popen close_fds behaviour differs between 3.2 and 3.4

Changes by Mike Sampson : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue23288] subprocess.Popen close_fds behaviour differs between 3.2 and 3.4

Mike Sampson added the comment: Ah, got it. Didn't see the note on the os.pipe() docs. Thanks. Closing. Sorry for the noise. -- ___ Python tracker ___ __

[issue23288] subprocess.Popen close_fds behaviour differs between 3.2 and 3.4

STINNER Victor added the comment: https://docs.python.org/dev/library/os.html#os.pipe Changed in version 3.4: The new file descriptors are now non-inheritable. If you don't use the subprocess module, you may use os.set_inheritable(). https://docs.python.org/dev/library/os.html#os.set_inheritabl

[issue23288] subprocess.Popen close_fds behaviour differs between 3.2 and 3.4

STINNER Victor added the comment: File descriptors are not closed, but not inherited neither, in Python 3.4. See the PEP 446. To have a reliable behaviour on all platforms and all Python versions, just use the pass_fds parameter. -- nosy: +haypo __

[issue23288] subprocess.Popen close_fds behaviour differs between 3.2 and 3.4

New submission from Mike Sampson: I'm seeing differing behaviour with subprocess.Popen(..., close_fds = False) between 3.2 and 3.4. The docs don't say this is meant to be the case as far as I can see. Python 3.2.3 on Debian Wheezy = >>> import subprocess >>> import