➜

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 stutzbach
Recipients bquinlan, stutzbach
Date 2010-11-16.19:36:12
SpamBayes Score 0.0005585205
Marked as misclassified No
Message-id <1289936174.35.0.332227808259.issue10437@psf.upfronthosting.co.za>
In-reply-to
Content 
ProcessPoolExecutor allows the max_workers parameter to the constructor to be omitted or None, in which case it will set the max_workers based on the number of CPUs.

It would be nice if ThreadPoolExecutor's constructor worked the same way; having the same interface is one of the wonderful things about this pair of classes.

I have a patch pretty much ready (with tests and a doc update), but it causes concurrent/futures/thread.py to import multiprocessing.  Were you trying to avoid that?
History
Date User Action Args
2010-11-16 19:36:14stutzbachsetrecipients: + stutzbach, bquinlan
2010-11-16 19:36:14stutzbachsetmessageid: <1289936174.35.0.332227808259.issue10437@psf.upfronthosting.co.za>
2010-11-16 19:36:12stutzbachlinkissue10437 messages
2010-11-16 19:36:12stutzbachcreate