Message 242120 - Python tracker

➜

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.

In-reply-to
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	<1430147230.91.0.128638057008.issue15064@psf.upfronthosting.co.za>

Content
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.

Content

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.

History
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

homepage