[issue10437] ThreadPoolExecutor should accept max_workers=None

Daniel Stutzbach report at bugs.python.org
Mon Nov 22 23:36:07 CET 2010


Daniel Stutzbach <stutzbach at google.com> added the comment:

Amaury Forgeot d'Arc said:
> pypy does have a GIL!

D'oh.  That shows you how much I know about PyPy.  Make that "keep in mind that IronPython doesn't have a GIL". ;)

Brian Quinlan said:
> I think that using the number of CPUs for max_workers makes sense
> for you but won't for most users. So I wouldn't make it a default.

Fair enough.  Marking as invalid.

----------
resolution:  -> invalid
stage: needs patch -> committed/rejected
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10437>
_______________________________________


More information about the Python-bugs-list mailing list