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 pitrou
Recipients jnoller, pitrou
Date 2009-11-13.19:28:52
SpamBayes Score 0.027765566
Marked as misclassified No
Message-id <1258140534.04.0.0239961207692.issue7318@psf.upfronthosting.co.za>
In-reply-to
Content
SocketClient() in multiprocessing.connection loops endlessly when the
connection is refused. It shouldn't, and instead use a timeout.
This is especially annoying since SocketClient() can be called as part
of finalizing an object, which makes debugging very annoying (see
issue7060).
History
Date User Action Args
2009-11-13 19:28:54pitrousetrecipients: + pitrou, jnoller
2009-11-13 19:28:54pitrousetmessageid: <1258140534.04.0.0239961207692.issue7318@psf.upfronthosting.co.za>
2009-11-13 19:28:52pitroulinkissue7318 messages
2009-11-13 19:28:52pitroucreate