Threads in Python version 1.5, thread doesn't start until calling process dies

Ken Tabacchi kentabacchi at
Thu Jul 26 10:03:38 EDT 2001

Sorry about the omission of key information.  My system is Windows NT
4.0.  The Python interpreter is version 1.5.1, and, if this means
anything, it is the interpreter that came with a dSPACE Control Desk
version 1.1 package.

Something interesting I discovered this morning, my implementation of
the thread module works as expected when run in Pythonwin (1.5.1), but
gives the erroneous result (thread doesn't start until process that
called it has died) when run in the Control Desk environment.  I'm not
sure about which interpreter Control Desk is using, although they site in their Help, About menu, but I think that number means
something only to dSPACE people.  Both Pythonwin and Control Desk
versions report the following when sys.version is called:

   '1.5.1 (#0, Jan 27 1999, 11:10:46) [MSC 32 bit (Intel)]'

Same interpreter yet different result.  It has been suggested to use
the threading module for a more 'predictable' execution.  Does anyone
have any advice about simply starting a new thread, exiting a thread
and possibly acquiring a lock using the threading module?  Much

James Logajan <JamesL at Lugoj.Com> wrote in message news:<3B5EE94B.1EBA28FF at Lugoj.Com>...
> That does look odd. What operating system are you using? And when you say
> 1.5, do you mean 1.5 or 1.5.2?
> Ken Tabacchi wrote:
> > 
> > I am having some trouble with a threadded process in Python version
> > 1.5.  It seems that the thread does not start until the calling
> > process has died.  The thread starts immediately when the following
> > program is run under Python version 2.1.
>  [ Elided. ]

More information about the Python-list mailing list