Author Hans Lawrenz
Recipients Hans Lawrenz, gvanrossum, vstinner, yselivanov
Date 2016-04-18.14:43:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1460990639.79.0.271352232569.issue26796@psf.upfronthosting.co.za>
In-reply-to
Content
In issue 21527 <http://bugs.python.org/issue21527> the concurrent.futures.ThreadPoolExecutor was changed to have a default value for max_workers. When asyncio.base_events.BaseEventLoop.run_in_executor creates a default ThreadPoolExecutor it specifies a value of 5 for max_workers, presumably because at the time it was written ThreadPoolExecutor didn't have a default for max_workers. This is confusing because on reading the documentation for ThreadPoolExecutor one might assume that the default specified there is what will be used if a default executor isn't supplied via BaseEventLoop.set_default_executor.

I propose that BaseEventLoop.run_in_executor be changed to not supply a default for max_workers. If this isn't acceptable, a note ought to be put in the run_in_executor documentation.
History
Date User Action Args
2016-04-18 14:43:59Hans Lawrenzsetrecipients: + Hans Lawrenz, gvanrossum, vstinner, yselivanov
2016-04-18 14:43:59Hans Lawrenzsetmessageid: <1460990639.79.0.271352232569.issue26796@psf.upfronthosting.co.za>
2016-04-18 14:43:59Hans Lawrenzlinkissue26796 messages
2016-04-18 14:43:59Hans Lawrenzcreate