[issue3006] subprocess.Popen causes socket to remain open after close

Charles-François Natali added the comment: It's fixed now that subprocess defaults to close_fds=True. -- resolution: -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker __

[issue3006] subprocess.Popen causes socket to remain open after close

Changes by Terry J. Reedy : -- versions: +Python 3.3 -Python 2.6, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue3006] subprocess.Popen causes socket to remain open after close

Charles-Francois Natali added the comment: > I cannot figure out why the closesocket's graceful shutdown is waiting for the Popen command to complete. It doesn't. Your main process closes its socket. You could see it with a netstat/lsof (don't know under Windows). The problem is that when you

[issue3006] subprocess.Popen causes socket to remain open after close

Changes by Terry J. Reedy : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 3.0 ___ Python tracker ___ ___ Python-bugs-list ma

[issue3006] subprocess.Popen causes socket to remain open after close

Changes by Nicolas Grilly <[EMAIL PROTECTED]>: -- nosy: +ngrilly ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue3006] subprocess.Popen causes socket to remain open after close

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > It's not perfect--another thread could still spawn a subprocess in > between Then it could be done in socketmodule.c, when still holding the GIL. Python code can change back the socket to inheritable afterwards if it wants to. > We probabl

[issue3006] subprocess.Popen causes socket to remain open after close

Kevin Watters <[EMAIL PROTECTED]> added the comment: I found a workaround for this issue (attached) via the kernel32.dll function SetHandleInformation. You can patch the socket class to set all newly created sockets as uninheritable. It's not perfect--another thread could still spawn a subproces

[issue3006] subprocess.Popen causes socket to remain open after close

Changes by Kevin Watters <[EMAIL PROTECTED]>: -- nosy: +kevinwatters ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mai

[issue3006] subprocess.Popen causes socket to remain open after close

New submission from Matt Mulsow <[EMAIL PROTECTED]>: On Windows, when a suprocess.Popen command is issued while a socket connection is being handled the socket connection will not close until the output of the subprocess is consumed. The connection remains open even though the request.close() com