This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kristjan.jonsson
Recipients kristjan.jonsson, sbt
Date 2013-05-13.15:28:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368458892.2.0.450730633923.issue17969@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2013-05-13 15:28:12kristjan.jonssonsetrecipients: + kristjan.jonsson, sbt
2013-05-13 15:28:12kristjan.jonssonsetmessageid: <1368458892.2.0.450730633923.issue17969@psf.upfronthosting.co.za>
2013-05-13 15:28:12kristjan.jonssonlinkissue17969 messages
2013-05-13 15:28:12kristjan.jonssoncreate