Message 351384 - 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	yselivanov
Recipients	aeros, asvetlov, lukasz.langa, vstinner, yselivanov
Date	2019-09-09.09:43:07
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1568022187.35.0.995890760512.issue34037@roundup.psfhosted.org>
In-reply-to

Content
Here's the API I propose to solve this problem: https://github.com/python/cpython/pull/15735#pullrequestreview-285389412 Summary: * Add a new loop.shutdown_threadpool() method. Just like with shutdown_asyncgens() -- it would be invalid to call loop.run_in_executer() after loop.shutdown_threadpool() is called. * Make asyncio.run() to call the new loop.shutdown_threadpool().

Here's the API I propose to solve this problem: https://github.com/python/cpython/pull/15735#pullrequestreview-285389412

Summary:

* Add a new loop.shutdown_threadpool() method. Just like with shutdown_asyncgens() -- it would be invalid to call loop.run_in_executer() after loop.shutdown_threadpool() is called.

* Make asyncio.run() to call the new loop.shutdown_threadpool().

History
Date	User	Action	Args
2019-09-09 09:43:07	yselivanov	set	recipients: + yselivanov, vstinner, asvetlov, lukasz.langa, aeros
2019-09-09 09:43:07	yselivanov	set	messageid: <1568022187.35.0.995890760512.issue34037@roundup.psfhosted.org>
2019-09-09 09:43:07	yselivanov	link	issue34037 messages
2019-09-09 09:43:07	yselivanov	create