Issue 36087: ThreadPoolExecutor max_workers none issue (original) (raw)

Issue36087

Created on 2019-02-23 01:44 by Tony Hammack, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 11994 closed python-dev,2019-02-23 01:54
Messages (3)
msg336354 - (view) Author: Tony Hammack (Tony Hammack) Date: 2019-02-23 01:44
ThreadPoolExecutor(max_workers=None) throws exception when it should not. Inconsistent with 3.4 documentation. If max_workers=None, then it should use the amount of cpus as threadcount.
msg336360 - (view) Author: Karthikeyan Singaravelan (xtreak) * (Python committer) Date: 2019-02-23 05:05
Thanks for the report. 3.4 is in security fixes only mode and will reach end of life soon. This seems to be a backport of the change in 3.5 that won't be accepted. Since the feature is available in 3.5+ I would recommend upgrading to 3.5 and above and to close this issue.
msg336377 - (view) Author: Andrew Svetlov (asvetlov) * (Python committer) Date: 2019-02-23 10:22
Please use the correct documentation version for Python 3.4. https://docs.python.org/3.4/library/concurrent.futures.html doesn't mention the pool size auto-selection. The feature was added in Python 3.5 only. Also, Python 3.4 reached the end-of-life, this version is not supported anymore.
History
Date User Action Args
2022-04-11 14:59:11 admin set github: 80268
2019-02-23 10:22:12 asvetlov set status: open -> closedtype: crash -> enhancementnosy: + asvetlovmessages: + resolution: not a bugstage: patch review -> resolved
2019-02-23 05:05:52 xtreak set nosy: + xtreakmessages: +
2019-02-23 01:54:58 python-dev set keywords: + patchstage: patch reviewpull_requests: + <pull%5Frequest12018>
2019-02-23 01:44:30 Tony Hammack create