[issue43329] Multiprocessing Manager Client Not Reconnecting

Michael L. Boom added the comment: Is there anything that I can do, or the company I work for can do, to get a developer assigned to fix this bug? It is hard to use multiprocessing remote method calls without this bug being fixed. The software wouldn't be robust enough for production. ---

[issue43329] Multiprocessing Manager Client Not Reconnecting

Ethan Furman added the comment: Here is the test, reduced and in a single script: --- 8< import multiprocessing.managers, os, sys, time if __name__ == '__main__': address = ("127.0.0.1", 54321) class TestManager(mul

[issue43329] Multiprocessing Manager Client Not Reconnecting

Michael L. Boom added the comment: I don't think I even got this working on the small scale. The unit test in the bug report is about as small as it gets and it doesn't work. The issue still exists in Python 3.9.5. -- ___ Python tracker

[issue43329] Multiprocessing Manager Client Not Reconnecting

Ethan Furman added the comment: Michael Boon wrote: --- > The [above] issue is pretty serious and it is preventing me from using a > system I wrote on a larger scale. That statement suggests you were able to get this working on a small scale -- is that correct? What does the

[issue43329] Multiprocessing Manager Client Not Reconnecting

New submission from Michael L. Boom : The client doesn't reconnect automatically, or explicitly. I just get BrokenPipeError over and over. Manager: import multiprocessing.managers, os, sys, time class TestClass(object): def test_method(self): print("In test_method