Message 341352 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	asvetlov
Recipients	asvetlov, yselivanov
Date	2019-05-03.19:22:03
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1556911323.77.0.733439136682.issue32309@roundup.psfhosted.org>
In-reply-to

Content
In Python 3.7 loop.run_in_executor() is the only user-faced method that requires a loop. asyncio.ThreadPool() sounds great. Maybe thread group can provide better api. But for Python 3.8 adding `run_in_executor` top-level function looks the only easy and obvious way to help people getting rid of explicit loop usage. Yuri, what do you think?

In Python 3.7 loop.run_in_executor() is the only user-faced method that requires a loop.

asyncio.ThreadPool() sounds great. Maybe thread group can provide better api.

But for Python 3.8 adding `run_in_executor` top-level function looks the only easy and obvious way to help people getting rid of explicit loop usage.

Yuri, what do you think?

History
Date	User	Action	Args
2019-05-03 19:22:03	asvetlov	set	recipients: + asvetlov, yselivanov
2019-05-03 19:22:03	asvetlov	set	messageid: <1556911323.77.0.733439136682.issue32309@roundup.psfhosted.org>
2019-05-03 19:22:03	asvetlov	link	issue32309 messages
2019-05-03 19:22:03	asvetlov	create