STINNER Victor <[email protected]> added the comment:
Message on a stackoverflow thread:
"I have suffered from the same problem, even if connecting on localhost in
python 2.7.1. After a day of debugging i found the cause and a workaround:
Cause: BaseProxy class has thread local storage which caches the connection,
which is reused for future connections causing "broken pipe" errors even on
creating a new Manager
Workaround: Delete the cached connection before reconnecting
if address in BaseProxy._address_to_local:
del BaseProxy._address_to_local[self.address][0].connection"
http://stackoverflow.com/questions/3649458/broken-pipe-when-using-python-multiprocessing-managers-basemanager-syncmanager/5884967#5884967
---
See also maybe the (closed) issue #11663: multiprocessing doesn't detect killed
processes
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue12364>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
