This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dan.oreilly
Recipients dan.oreilly, python-dev, sbt, tshepang
Date 2015-04-27.15:07:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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:10dan.oreillysetrecipients: + dan.oreilly, tshepang, python-dev, sbt
2015-04-27 15:07:10dan.oreillysetmessageid: <>
2015-04-27 15:07:10dan.oreillylinkissue15064 messages
2015-04-27 15:07:10dan.oreillycreate