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 eric.snow
Recipients Ben.Darnell, aeros, eric.snow, pitrou, sa, vstinner
Date 2022-02-03.21:21:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643923316.58.0.332312205916.issue41962@roundup.psfhosted.org>
In-reply-to
Content
> I'm running some long-running (possibly infinite) tasks in the thread pool,
> and I cancel them in an `atexit` callback

Alternately, perhaps ThreadPoolExecutor isn't the right fit here, as implied by the route you ended up going.  It seems like it's not well-suited for long-running (or infinite) tasks.  In that case, perhaps the concurrent.futures docs could be more clear about when ThreadPoolExecutor is not a good fit and what the alternatives are.
History
Date User Action Args
2022-02-03 21:21:56eric.snowsetrecipients: + eric.snow, pitrou, vstinner, sa, Ben.Darnell, aeros
2022-02-03 21:21:56eric.snowsetmessageid: <1643923316.58.0.332312205916.issue41962@roundup.psfhosted.org>
2022-02-03 21:21:56eric.snowlinkissue41962 messages
2022-02-03 21:21:56eric.snowcreate
Morty Proxy This is a proxified and sanitized view of the page, visit original site.