You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee=Noneclosed_at=<Date2014-09-02.17:39:27.734>created_at=<Date2014-05-18.22:47:47.410>labels= ['type-feature', 'library']
title='concurrent.futures.ThreadPoolExecutor does not use a default value'updated_at=<Date2014-09-02.17:39:27.732>user='https://github.com/PCManticore'
As the title says, ThreadPoolExecutor does not use a default value for max_workers parameter, as ProcessPoolExecutor does. When the user does not care about the number of workers and wants only for something to run in background, he has to write code like this:
executor=ThreadPoolExecutor(1) # or any other value
This situation can also occur when the class is passed as a factory function: