Kristján Valur Jónsson added the comment: I think that socket.close() is the exception rather than the rule here. What kind of handle is this? It can't be a socket, since that would require closesocket.
Also, even though an IO call _can_ block, that doesn't mean that we _must_ release the gil for the duration. I´m not very familiar with multiprocessing, I'm mainly trying to enhance robustness with our build tools here. Would an alternative fix, making the worker thread a non-daemon, be hard to do? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17969> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
