[issue18751] A manager's server never joins its threads

Changes by Ned Deily : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue18751] A manager's server never joins its threads

Yusuke Tsutsumi added the comment: I'm interested in taking this on. I can do the following: * keep track of the threads in a field attached to the class * handle thread synchronization and cleanup in the finally block * set a flag on the exception, which ensures the loop completes, vs immediate

[issue18751] A manager's server never joins its threads

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue18751] A manager's server never joins its threads

Gregory P. Smith added the comment: Capturing some notes from looking at this after Dan Sully asked me questions about the issue during today's pycon sprints: within multiprocessing/managers.py serve_forever(): the accepter thread is an infinite loop. i think this issue also wants to join() o

[issue18751] A manager's server never joins its threads

Mark Lawrence added the comment: I've checked the code and this doesn't appear to have been implemented. I looked into providing a patch myself, but all the returns from calls to util.Finalize that I could find were assigned to different attribute names, so I'm not confident enough to proceed

[issue18751] A manager's server never joins its threads

New submission from Antoine Pitrou: The Server class in multiprocessing.managers creates daemon threads and never joins them. This is in contrast with e.g. the Pool class, which creates daemon threads but uses util.Finalize to join them. (not joining daemon threads may have adverse effects suc