[issue6056] socket.setdefaulttimeout affecting multiprocessing Manager
report at bugs.python.org
Tue Jun 7 16:52:09 CEST 2011
Derek Wilson <jderekwilson at gmail.com> added the comment:
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.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list