Home Original page

simple thread problem

Robert Cragie rcc at nospamthanks_jennic.com
Mon Jun 19 12:48:19 EDT 2000 
The mysterious message you get is when 'threading' encounters threads
created in 'thread', so it sounds to me that you are mixing 'threading' and
'thread' objects - are you using 'threading.Semaphore' or such like? As Aahz
says, try to do it all using 'threading' objects.

BTW, it's not actually a problem as such - it will probably still work.
'threading' calls these 'Dummy threads' - look at threading.py for more
info.

Robert Cragie

Aahz Maruch <aahz at netcom.com> wrote in message
news:8ilbfp$6a8$1 at nntp9.atl.mindspring.net...
| In article <394E2F9C.6BCD96B5 at iue.tuwien.ac.at>,
| Markus Gritsch  <gritsch at iue.tuwien.ac.at> wrote:
| >
| >I started a very simple program to get familiar with Python threads.
| >It works fine, except for some misterious messages which I get every
| >time a thread exits:
| >
| >currentThread(): no current thread for xxxx
|
| I'm not sure how to tell you to fix the problem in your current context;
| instead, let me push you strongly to subclass threading.Thread() instead
| of using the thread module.  I guarantee this will make your life a lot
| simpler.  If you still have trouble, come back here and I'll show you
| how to do your example using Thread().
| --
|                       --- Aahz (Copyright 2000 by aahz at netcom.com)
|
| Androgynous poly kinky vanilla queer het    <*>
http://www.rahul.net/aahz/
| Hugs and backrubs -- I break Rule 6
|
| "The only problem with Microsoft is they just have no taste." --Steve Jobs
| (From _Triumph of the Nerds_ PBS special)
More information about the Python-list mailing list