[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Changes by Andre Merzky : Added file: http://bugs.python.org/file40449/subprocess.py.diff ___ Python tracker ___ ___ Python-bugs-list mailing

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Changes by Andre Merzky : Removed file: http://bugs.python.org/file40448/subprocess.py.diff ___ Python tracker ___ ___ Python-bugs-list mailin

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Andre Merzky added the comment: This is patch is meant to be illustrative rather than functional (but it works in the limited set of cases I tested). -- keywords: +patch Added file: http://bugs.python.org/file40448/subprocess.py.diff ___ Python track

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Andre Merzky added the comment: Yes, I have a workaround (and even a clean solution) in my code. My interest in this ticket is more academic than anything else :) Thanks for the pointer to issue1731717. While I am not sure which 'comment at the end' you exactly refer to, the whole discussion

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Gregory P. Smith added the comment: My gut feeling is to say "don't do that" when it comes to passing subprocess instances between processes (ie: pickling and unpickling them) and expecting them to work as if nothing had changed... You already acknowledge that this is a strange thing for an a

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

R. David Murray added the comment: Not really. Give GPS a couple more weeks to respond, and then maybe bring it up on python-dev. -- ___ Python tracker ___

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Andre Merzky added the comment: Hi again, can I do anything to help moving this forward? Thanks, Andre. -- ___ Python tracker ___ _

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Changes by R. David Murray : -- nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Andre Merzky added the comment: Looking a little further, it seems indeed to be a problem with ignoring SIGCHLD. The behavior has been introduced with [1] at [2] AFAICS, which is a response to issue15756 [3]. IMHO, that issue should have been resolved with raising an exception instead of ass

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Andre Merzky added the comment: As mentioned in the PS, I understand that the approach might be questionable. But (a) the attached test shows the problem also for watcher *processes*, not threads, and (b) an error should be raised in unsupported uses, not a silent, unexpected behavior which m

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

R. David Murray added the comment: I'll let someone else analyze this in detail if they want to, but I'll just note that mixing multiprocessing and threads is not a good idea and will lead to all sorts of strangeness. Especially if you are using the unix default of fork for multiprocessing.

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

New submission from Andre Merzky: - create a class which is a subclass of multiprocessing.Process ('A') - in its __init__ create new thread ('B') and share a queue with it - in A's run() method, run 'C=subprocess.Popen(args="/bin/false")' - push 'C' though the queue to 'B' - call 'C.pull()' -