Logged In: YES 
user_id=357491

To force this error I inserted code to set all attributes of the threading 
module to None and then throw and exception.  After commenting out 
the two calls to currentThread in _Condition the thrown exception to 
trigger the problem propogated to the top correctly.

I did have the clean-up function give out since I set *everything* to 
None, but it doesn't look like a normal issue as shown in the exception 
traceback in the OP.  I don't think it is an issue.

So it seems commenting the two calls to currentThread in _Condition 
solves the problem.  But since this is threading code and the comment 
explicitly states it is for the side-effect I am going to try to get a second 
opinion.