[issue34785] pty.spawn -- auto-termination after child process is dead (a zombie)

Jarry Shaw added the comment: This issue is duplicated with issue26228, sorry. -- stage: patch review -> resolved status: pending -> closed ___ Python tracker ___

[issue34785] pty.spawn -- auto-termination after child process is dead (a zombie)

Martin Panter added the comment: Suggest closing this assuming it is a duplicate, unless Jarry can give more information. -- resolution: -> duplicate status: open -> pending superseder: -> pty.spawn hangs on FreeBSD 9.3, 10.x ___ Python tracker

[issue34785] pty.spawn -- auto-termination after child process is dead (a zombie)

Martin Panter added the comment: Is this to get “spawn” working on a non-Linux platform like a recent Free BSD, OS X, or Solaris? If so, see Issue 26228. If not, you might have to explain your use case better. Polling for the child exiting is going to race with handling the child’s output,

[issue34785] pty.spawn -- auto-termination after child process is dead (a zombie)

Change by Jarry Shaw : -- pull_requests: +8930 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue34785] pty.spawn -- auto-termination after child process is dead (a zombie)

New submission from Jarry Shaw : As in pty.spawn, once started, the parent process will be hanged, even if the child process is already dead (or a zombie), and must wait for a KeyboardInterrupt or else to terminate the whole process. Thus, I propose to revise `_copy` function, where the