New submission from Daniel Stutzbach <stutzb...@google.com>:

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?

----------
assignee: stutzbach
components: Library (Lib)
messages: 121311
nosy: bquinlan, stutzbach
priority: normal
severity: normal
stage: needs patch
status: open
title: ThreadPoolExecutor should accept max_workers=None
type: behavior
versions: Python 3.2

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue10437>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to