[issue29954] multiprocessing.Pool.__exit__() calls terminate() instead of close()

Antoine Pitrou added the comment: I agree it's far too late. Multiple existing libraries may rely on the current behaviour. -- nosy: +pitrou resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker

[issue29954] multiprocessing.Pool.__exit__() calls terminate() instead of close()

Josh Rosenberg added the comment: I suspect it's far too late to change this, given compatibility constraints. If you want it to close instead of terminate, contextlib.closing is always an option. -- nosy: +josh.r ___ Python tracker

[issue29954] multiprocessing.Pool.__exit__() calls terminate() instead of close()

Changes by Xiang Zhang : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue29954] multiprocessing.Pool.__exit__() calls terminate() instead of close()

New submission from Petr Zemek: multiprocessing.Pool.__exit__() calls terminate() instead of close(). Why? Wouldn't it be better (and more expected from a user's point of view) if it called close()? Reasons: - Calling close() would wait until all tasks are completed before shutting down the