New submission from Jonas Weismüller <[email protected]>:
If socket.setdefaulttimeout is set to any value (except None), the BaseManager
raises an exception and the execution of the remote object fails:
Traceback (most recent call last):
File "client.py", line 16, in <module>
m = Manager()
File "client.py", line 12, in __init__
self.connect()
File "/usr/lib/python2.6/multiprocessing/managers.py", line 474, in connect
conn = Client(self._address, authkey=self._authkey)
File "/usr/lib/python2.6/multiprocessing/connection.py", line 140, in Client
answer_challenge(c, authkey)
File "/usr/lib/python2.6/multiprocessing/connection.py", line 371, in
answer_challenge
message = connection.recv_bytes(256) # reject large message
See the attached client.py (uploading soon) and server.py file to reproduce the
error.
Python version used:
Python 2.6 (r26:66714, Jun 8 2009, 16:07:26)
[GCC 4.4.0 20090506 (Red Hat 4.4.0-4)] on linux2
Same behaviour with python version:
Python 2.6 (r26:66714, Nov 3 2009, 17:33:38)
[GCC 4.4.1 20090725 (Red Hat 4.4.1-2)] on linux2
The operating system is Fedora 11.
----------
components: Library (Lib)
files: server.py
messages: 98427
nosy: MrRagga
severity: normal
status: open
title: BaseManager of multiprocessing module throws an exception if
socket.setdefaulttimeout is set
type: crash
versions: Python 2.6
Added file: http://bugs.python.org/file16025/server.py
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue7795>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
