win98 spawnv vs execv

[Chris Gonnerman]

The exec family of functions terminate the Python interpreter and replace
it with the called program; spawnv starts an additional process.  

os.execv() is a Unixism, used together with os.fork() to start new
processes.  My best guess is, PythonWin simply isn't designed to 
"keel over" when os.execv() is called.

As the doctor says, if it hurts when you do that, don't do that.

BTW when you post to the list about error messages, you probably 
should post at least the first sentence or two of the actual error message
*verbatim* as Windows has thousands of messages that don't always
mean what they say.

----- Original Message ----- 
From: "zzzzz" <zzizz_ at notmail.com>
Newsgroups: comp.lang.python
To: <python-list at python.org>
Sent: Saturday, February 24, 2001 5:50 PM
Subject: win98 spawnv vs execv


> Hi all,
> I running be-open python 2.0 with pythonwin on win98 and get an
> windows execption when I launch a program with os.execv causing
> pythonwin to immediately close... even though the program is
> succefully launched. However, when I use os.spawnv with a os.P_WAIT
> option the function works fine.
> 
> Is this likely to be:
> a) a platform limitation,
> b) something to do with my computer (I run Nortons Anti-Virus 5.0 not
> 2000 and I don't think I'm launching popen*),
> c) something else I've haven't thought of, or
> d) stop making up other options.