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 r.david.murray
Recipients docs@python, etuardu, r.david.murray
Date 2011-09-30.15:42:48
SpamBayes Score 8.569651e-06
Marked as misclassified No
Message-id <1317397369.0.0.79874621126.issue13077@psf.upfronthosting.co.za>
In-reply-to
Content
It seems clear enough to me that when a process terminates ("the entire Python program exits") then all of its threads must terminate.  That's part of the definition of threads, to my understanding.

I think the confusion arises from the use of the word "deamon", which has been discussed as a bad thing elsewhere in this tracker.  A unix user would expect a "daemon" to keep running in the background, whereas here it is exactly the opposite.  See issue 5906 for example, where in the context of Multiprocessing it becomes even more confusing.  Perhaps a similar note that 'daemon' does not mean what it does in unix would be a good idea.
History
Date User Action Args
2011-09-30 15:42:49r.david.murraysetrecipients: + r.david.murray, docs@python, etuardu
2011-09-30 15:42:49r.david.murraysetmessageid: <1317397369.0.0.79874621126.issue13077@psf.upfronthosting.co.za>
2011-09-30 15:42:48r.david.murraylinkissue13077 messages
2011-09-30 15:42:48r.david.murraycreate