This repository has been archived by the owner on Nov 29, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use daemon mode to circrumvent a memory leak (reported at https://bugs.python.org/issue37193).
Daemonic threads are killed immediately on shutdown by the python interpreter without waiting for until they are finished.
Maybe block_on_close = True could work too. In that case the interpreter waits for the threads to finish but doesn't track them in the _threads list.
It seems that the interpreter always waits for non-daemonic threads before finishing. Therefore I currently wonder why the Python devs added thread joining to the ThreadingMixIn (https://github.com/python/cpython/blob/3.7/Lib/socketserver.py#L674) at all when it is done on shutdown automatically already.
Short example script (works with Python 2.7 too) for playing with the different threading behavior.