Memeplex added the comment: One possible fix to multiprocessing/process.py:
< try: < self.run() < exitcode = 0 < finally: < util._exit_function() --- > self.run() > exitcode = 0 274a272 > util._exit_function() This removes the try/finally pair around self.run() and calls _exit_function in the last finally clause. It doesn't honour the original control flow, as this last clause is even executed when the flow is aborted before reaching self.run(). That said, I can't see any particular reason to prefer the original flow. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24948> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
