Message189145
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? |
|
Date |
User |
Action |
Args |
2013-05-13 15:28:12 | kristjan.jonsson | set | recipients:
+ kristjan.jonsson, sbt |
2013-05-13 15:28:12 | kristjan.jonsson | set | messageid: <1368458892.2.0.450730633923.issue17969@psf.upfronthosting.co.za> |
2013-05-13 15:28:12 | kristjan.jonsson | link | issue17969 messages |
2013-05-13 15:28:12 | kristjan.jonsson | create | |
|