[issue36087] ThreadPoolExecutor max_workers none issue

Andrew Svetlov added the comment: 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 ver

[issue36087] ThreadPoolExecutor max_workers none issue

Karthikeyan Singaravelan added the comment: 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

[issue36087] ThreadPoolExecutor max_workers none issue

Change by Roundup Robot : -- keywords: +patch pull_requests: +12018 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-l

[issue36087] ThreadPoolExecutor max_workers none issue

New submission from Tony Hammack : 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. -- components: Library (Lib) messages: 336354 nosy: Tony Hammack