➜

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 aeros
Recipients aeros, asvetlov, primal, yselivanov
Date 2019-11-01.11:33:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572607980.23.0.32837958185.issue32309@roundup.psfhosted.org>
In-reply-to
Content 
Actually, I think it would be better to move the functionality of loop.shutdown_default_executor() to a new private method loop._shutdown_executor() that takes an executor argument rather than shutting down the default one. This could be used in both loop.shutdown_default_executor() and ThreadPool. There's no need to move it to function instead of being a method of BaseEventLoop though, that doesn't make sense now that I think about it more. 

Sorry if my thoughts are a bit disorganized, I think I need to get some sleep. (:
History
Date User Action Args
2019-11-01 11:33:00aerossetrecipients: + aeros, asvetlov, yselivanov, primal
2019-11-01 11:33:00aerossetmessageid: <1572607980.23.0.32837958185.issue32309@roundup.psfhosted.org>
2019-11-01 11:33:00aeroslinkissue32309 messages
2019-11-01 11:33:00aeroscreate