Problems with threads

[Gary Duzan]

Jonathan Giddy wrote:
> 
> Dominic Hillenbrand <I-C-H at gmx.de> writes:
> >This code produces this type of error message:
> 
> >currentThread(): no current thread for 1025
> >currentThread(): no current thread for 2050
> >(.....)
> 
> >The program still seems to run correct!!!
> >But what is the reason for the error message?
> 
> It is an interaction between the builtin thread module and the threading
> module.  If you start your threads using the threading.Thread class, the
> message will not appear.
> 
> Essentially, this is a warning from threading.py that there is no Thread
> instance representing this thread.

   However, depending on your code, this may be a perfectly valid
state, and threading handles it reasonably well, but there is no
way to turn off the message short of editing threading.py, which
we did here. This should really be fixed in a future release.

					Gary Duzan
					GTE Laboratories