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 underrun
Recipients asksol, jnoller, ryles, underrun
Date 2011-06-07.14:52:08
SpamBayes Score 9.62563e-06
Marked as misclassified No
Message-id <>
This should be higher priority as one of the major benefits of the multiprocessing module is remote process management in a completely transparent manner. socket timeouts are very important in this context as blocking forever waiting for a connection is not always an option. 

The problem of not being able to use a default socket timeout for other purposes in combination with multiprocessing managers is definitely an issue, but making multiprocessing actually use the timeout itself if set would be a huge advantage.

This might not be the place to ask for it, but it would make sense for manager objects to gain a timeout attribute to be used as a timeout for local or remote communications. At the very least, the manager.connect() method should accept a timeout argument.
Date User Action Args
2011-06-07 14:52:09underrunsetrecipients: + underrun, jnoller, ryles, asksol
2011-06-07 14:52:09underrunsetmessageid: <>
2011-06-07 14:52:09underrunlinkissue6056 messages
2011-06-07 14:52:08underruncreate