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.

classification
Title: logging.handlers: Document that QueueListener is a daemon thread
Type: enhancement Stage: resolved
Components: Documentation Versions: Python 3.8, Python 3.7
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, drlazor8, vinay.sajip, xtreak
Priority: normal Keywords:

Created on 2016-12-06 20:27 by drlazor8, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg346056 - (view) Author: Vinay Sajip (vinay.sajip) * (Python committer) Date: 2019-06-19 14:59
Why does that particularly need documenting? If it were a non-daemon thread, that might need documenting as the program would have to join() it or else seem to hang, but what does it matter if it's a daemon thread?
msg346186 - (view) Author: Julien Castiaux (drlazor8) * Date: 2019-06-21 07:21
Hello,

The purpose of the QueueListener is to provide a way to get messages sent by QueueHandlers. I was starting the QueueListener in is own mp.Process and was expecting the start() to hang. As it was not, the process was exiting logging a few messages or not depending on the threads schedule. I had a difficult time debugging it and ended up looking at the source code as the start() method was not stating it was starting a daemon thread.

The documentation now states it, I close the bug.
Regards,
History
Date User Action Args
2022-04-11 14:58:40adminsetgithub: 73076
2019-06-21 07:28:34vinay.sajipsetstatus: open -> closed
stage: resolved
2019-06-21 07:21:03drlazor8setresolution: out of date
messages: + msg346186
2019-06-19 14:59:55vinay.sajipsetmessages: + msg346056
2019-01-23 13:53:51xtreaksetnosy: + vinay.sajip, xtreak

versions: + Python 3.7, Python 3.8, - Python 3.5
2016-12-06 20:27:33drlazor8create