Message249264
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. |
|
Date |
User |
Action |
Args |
2015-08-27 21:41:59 | memeplex | set | recipients:
+ memeplex |
2015-08-27 21:41:59 | memeplex | set | messageid: <1440711719.46.0.387537258471.issue24948@psf.upfronthosting.co.za> |
2015-08-27 21:41:59 | memeplex | link | issue24948 messages |
2015-08-27 21:41:59 | memeplex | create | |
|