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 gpolo
Recipients gpolo
Date 2008-10-23.20:28:20
SpamBayes Score 0.0074599953
Marked as misclassified No
Message-id <1224793703.28.0.169476277835.issue4188@psf.upfronthosting.co.za>
In-reply-to
Content
Lib/threading.py gets into infinite recursion while testing (or using)
it with verbose set. This didn't happen before because Thread.__started
didn't use to be an Event, but now it is.

Typical situation:
_DummyThread calls _Thread__started.set, which calls
__started.__cond.notify_all(), which calls __cond.notify(). If there are
no waiters, it calls _Verbose._note, which calls currentThread, but if
there is no current thread _DummyThread is called, which calls
_Thread__started.set ...
History
Date User Action Args
2008-10-23 20:28:23gpolosetrecipients: + gpolo
2008-10-23 20:28:23gpolosetmessageid: <1224793703.28.0.169476277835.issue4188@psf.upfronthosting.co.za>
2008-10-23 20:28:22gpololinkissue4188 messages
2008-10-23 20:28:21gpolocreate