Message242120
It's probably too late to do anything about this now, but wouldn't it make more sense for `Pool.__exit__` to call `close`, rather than `terminate`? The vast majority of the time, that's probably what the user of the `Pool` would want to run. It also would make the behavior consistent with `concurrent.futures.ProcessPoolExecutor`, which will always wait for pending tasks to complete before exiting the `with` block. |
|
Date |
User |
Action |
Args |
2015-04-27 15:07:10 | dan.oreilly | set | recipients:
+ dan.oreilly, tshepang, python-dev, sbt |
2015-04-27 15:07:10 | dan.oreilly | set | messageid: <1430147230.91.0.128638057008.issue15064@psf.upfronthosting.co.za> |
2015-04-27 15:07:10 | dan.oreilly | link | issue15064 messages |
2015-04-27 15:07:10 | dan.oreilly | create | |
|