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 Sandy Chapman, docs@python, r.david.murray
Date 2015-05-27.13:27:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432733250.84.0.270504940836.issue24296@psf.upfronthosting.co.za>
In-reply-to
Content
If you know anything about threads you can see that the threads are not explicitly shut down.  As a standalone example it is "correct", in that they get shut down at interpreter shutdown.

I'm not sure it is appropriate to include what is essentially a thread tutorial note in the queue docs.  A crosslink to threading would certainly be a good idea; perhaps the introductory sentence could be tweaked to point people who don't already know threads in the correct direction for enlightenment.
History
Date User Action Args
2015-05-27 13:27:30r.david.murraysetrecipients: + r.david.murray, docs@python, Sandy Chapman
2015-05-27 13:27:30r.david.murraysetmessageid: <1432733250.84.0.270504940836.issue24296@psf.upfronthosting.co.za>
2015-05-27 13:27:30r.david.murraylinkissue24296 messages
2015-05-27 13:27:30r.david.murraycreate