Author memeplex
Recipients memeplex
Date 2015-08-27.21:41:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440711719.46.0.387537258471.issue24948@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2015-08-27 21:41:59memeplexsetrecipients: + memeplex
2015-08-27 21:41:59memeplexsetmessageid: <1440711719.46.0.387537258471.issue24948@psf.upfronthosting.co.za>
2015-08-27 21:41:59memeplexlinkissue24948 messages
2015-08-27 21:41:59memeplexcreate