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 Tamas.K, bkabrda, csernazs, grahamd, jcea, koobs, ncoghlan, neologix, pitrou, python-dev, tim.peters
Date 2013-09-08.17:58:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ah - the test used to do t.join(NUMTASKS)!  That's just bizarre ;-)

I believe I can repair that too (well - there was never a _guarantee_ that waiting 10 seconds would be long enough), but I'll wait until this all settles down.

join() and is_alive() are too complicated now, because of the 2-step dance to check whether the thread is done:  we have both an Event (_stopped) and a lock (_tstate_lock) to check now.  The Event doesn't serve a purpose anymore:  it's almost always uninteresting to know _just_ that the Python part of the thread has ended.  The only exception I can see is the perverse case of joining the main thread done in some of the tests (in that case we have to claim the main thread is done even though its tstate is still active).

Anyway, after getting rid of the Event it should be dead easy to make join(10) "appear to work the same as before, despite that it never really worked ;-)".
Date User Action Args
2013-09-08 17:58:10tim.peterssetrecipients: + tim.peters, jcea, csernazs, ncoghlan, pitrou, grahamd, neologix, python-dev, bkabrda, koobs, Tamas.K
2013-09-08 17:58:10tim.peterssetmessageid: <>
2013-09-08 17:58:10tim.peterslinkissue18808 messages
2013-09-08 17:58:09tim.peterscreate