How to open a patch with dup2 code#

Here is an attempt at a slightly more readable code by refactoring. Yes, but we can port it ourselves (unless you're really motivated)

Does this also need to be applied for 3.1? Self.assertEqual((out, err), (b'apple', b'orange')) Out, err = subprocess.Popen(.).communicate() Therefore you first have to strip that output, like this: Python adds extra output at the end of stderr when compiled in debug > Attached is a patch which basically uses fcntl if necessary to remove But, if we're using pipes, the close-on-exec flags are set initially and the dup2() call would normally remove the flag but it doesn't.Īttached is a patch which basically uses fcntl if necessary to remove the close-on-exec flag, and tests. If c2pwrite or p2cread or errwrite is the same as what it's being dupped() to (eg if c2pwrite = 1) then the dup2 call does nothing. The problem comes about where the calls are made (this applies to the python & c versions): (b'', b'Fatal Python error: Py_Initialize: can't initialize sys standard streams OSError: Bad file descriptor ') Res = subprocess.Popen([sys.executable, '-c',į.write(repr((b'apple', b'orange')) + ' ') This may actually be a fairly common use case in a daemon program that needs to run a subprocess and set up pipes to it. a daemon) and then uses the subprocess module, the file descriptors may not be set up properly in the subprocess. There is an issue where if a python program closes all the std. Georg.brandl, giampaolo.rodola, gregory.p.smith, pitrou, rosslagerwall, vstinnerĬreated on 18:08 by rosslagerwall, last changed 14:57 by admin.