Threading and Windows.

[Jorge Godoy]

Dennis Lee Bieber <wlfraed at ix.netcom.com> writes:

> Jorge Godoy fed this fish to the penguins on Monday 29 September 2003 
> 07:31 pm:
>
>> 
>> This isn't the behaviour I found here on a Linux box. The caller
>> process got 'stuck' and only worked again when the called proccess
>> ended.
>>
>         Strange...

I thought the same thing and even thought I was using os.spawnv() in a
wrong way. Even with the 'P_NOWAIT' flag it still hangs. 

I'm using:

Python 2.2.2 (#1, Mar  6 2003, 13:36:19)
[GCC 3.2.2] on linux-i386


I haven't investigated os.spawnv() alone in Windows to see if this
also happens there. It will be funny if by this very first time the
problem is on the Linux box instead of the Windows box (since I'm more
used to unices, I'm more familiar with their quirks than with
Windows', specially with all those 'flavours' of Windows...). 

>         I think NT has the ability to go by extension, but not W9x.

Windows XP can't go by extension either. 

>         You might have to explicitly invoke the python executable, and pass 
> /it/ the .py file as the first argument

I see. If it doesn't work using os.startfile() as suggested on another
message I'll probably stick with this approach. 


Thanks!

-- 
Godoy.     <godoy at metalab.unc.edu>