[issue42647] Unable to use concurrent.futures in atexit hook

Change by Dong-hee Na : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42647] Unable to use concurrent.futures in atexit hook

Julien Danjou added the comment: > Is there a real-world situation where it's specifically necessary or even > beneficial to utilize ThreadPoolExecutor at this point after thread > finalization rather than earlier in the program? Not that it doesn't exist, > but to me it intuitively seems

[issue42647] Unable to use concurrent.futures in atexit hook

Kyle Stanley added the comment: Thanks for bringing attention to this, Julien. While the regression is definitely unfortunate, I'm uncertain about whether the behavior is *correct* to allow in the first place. Specifically, allowing the registration of an atexit hook which uses a

[issue42647] Unable to use concurrent.futures in atexit hook

Change by Irit Katriel : -- nosy: +aeros ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42647] Unable to use concurrent.futures in atexit hook

Irit Katriel added the comment: b61b818d916942aad1f8f3e33181801c4a1ed14b is the first bad commit commit b61b818d916942aad1f8f3e33181801c4a1ed14b Author: Kyle Stanley Date: Fri Mar 27 15:31:22 2020 -0400 bpo-39812: Remove daemon threads in concurrent.futures (GH-19149) Remove

[issue42647] Unable to use concurrent.futures in atexit hook

New submission from Julien Danjou : Python 3.9 introduced a regression with concurrent.futures. The following program works fine on Python < 3.8 but raises an error on 3.9: ``` import atexit import concurrent.futures def spawn(): with concurrent.futures.ThreadPoolExecutor() as t: