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, dralley, sophia2, yselivanov
Date 2020-10-30.03:11:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1604027483.9.0.328637090803.issue41699@roundup.psfhosted.org>
In-reply-to
Content
> Regularly calling executor.shutdown() and then instantiating a new ThreadPoolExecutor in order to run an asyncio program does not seem like a good API to me.

Clarification: you're typically only supposed to instantiate a single ThreadPoolExecutor or ProcessPoolExecutor per program (sometimes one of each depending on use case), and continuously submit jobs to it rather than creating multiple executor instances. Otherwise, it's generally unneeded overhead.

(I'll take a look at the other parts once I find the time, just wanted to briefly mention the above in the meantime.)
History
Date User Action Args
2020-10-30 03:11:23aerossetrecipients: + aeros, asvetlov, yselivanov, sophia2, dralley
2020-10-30 03:11:23aerossetmessageid: <1604027483.9.0.328637090803.issue41699@roundup.psfhosted.org>
2020-10-30 03:11:23aeroslinkissue41699 messages
2020-10-30 03:11:23aeroscreate