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 tim.peters
Recipients davin, eryksun, neologix, pietvo, pitrou, sbt, tim.peters
Date 2016-07-14.03:24:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468466672.76.0.230889875286.issue18966@psf.upfronthosting.co.za>
In-reply-to
Content
About ""No parents, no children", that's fine so far as it goes.  But Python isn't C, a threading.Thread is not a POSIX thread, and threading.py _does_ have a concept of "the main thread".  There's no conceptual problem _in Python_ with saying "the main thread" waits to .join() other non-daemon threading.Threads at process exit.  No parent/child relationships are implied by that either - it's just the concept that one thread is distinguished.
History
Date User Action Args
2016-07-14 03:24:32tim.peterssetrecipients: + tim.peters, pitrou, pietvo, neologix, sbt, eryksun, davin
2016-07-14 03:24:32tim.peterssetmessageid: <1468466672.76.0.230889875286.issue18966@psf.upfronthosting.co.za>
2016-07-14 03:24:32tim.peterslinkissue18966 messages
2016-07-14 03:24:32tim.peterscreate