New submission from Luca Falavigna:
I have a program which waits for external events (mostly pyinotify events), and
when events occur a new worker is created using
concurrent.futures.ThreadPoolExecutor. The following snippet represents shortly
what my program does:
from time import sleep
Luca Falavigna added the comment:
There is indeed little benefit in freeing up resources left open by a unused
thread, but it could be worth closing it for specific needs (e.g. thread
processes sensible information) or in embedded systems with very low resources
