[issue9148] os.execve puts process to background on windows

Thomas Sibley added the comment: Thanks for taking the time to explain. I was just discovering the same myself experimentally. The MS docs I linked to seem a little misleading. orz In that case, do you think a doc patch for os.exec* adding a more nuanced take on Windows support would be

[issue9148] os.execve puts process to background on windows

Eryk Sun added the comment: nt.execv[e] wraps calling the C runtime _wexecv[e] function. The other os.exec* functions are in turn based on these calls. As to spawn, for Windows _P_OVERLAY just means to exit the current process. The source code is published, so you can see how simple the

[issue9148] os.execve puts process to background on windows

Thomas Sibley added the comment: It seems like it would be very nice to provide compat if its possible with a minimum of effort. At the very least, a doc patch to os.exec*() seems warranted. I expected to find notes on platform compat in the doc and was pleasantly surprised to see the

[issue9148] os.execve puts process to background on windows

Thomas Sibley added the comment: What about using _execv*() and friends, as documented at ? They appear to use the process overlay feature of _spawnv*() et al., as described at

[issue9148] os.execve puts process to background on windows

Eryk Sun added the comment: Python doesn't go out of its way to fake a cross-platform POSIX environment in Windows, complete with emulated fork and exec. I don't recommend using nt.execv[e] or the os.exec* functions in Windows. Their behavior is almost always undesired. I'd be in favor of

[issue9148] os.execve puts process to background on windows

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9148] os.execve puts process to background on windows

Change by Thomas Sibley : -- nosy: +trs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9148] os.execve puts process to background on windows

Mark Lawrence added the comment: I've changed the nosy list according to the experts index for the os module and Windows, sorry if I've named anyone I shouldn't have. -- nosy: +BreamoreBoy, loewis, steve.dower, tim.golden, zach.ware ___ Python

[issue9148] os.execve puts process to background on windows

Changes by Piotr Dobrogost p...@bugs.python.dobrogost.net: -- nosy: +piotr.dobrogost ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9148 ___ ___

[issue9148] os.execve puts process to background on windows

Changes by Matt Joiner anacro...@gmail.com: -- nosy: +anacrolix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9148 ___ ___ Python-bugs-list

[issue9148] os.execve puts process to background on windows

Piotr Dobrogost added the comment: This is unexpected and makes people wonder what's going on. See http://stackoverflow.com/q/7004687/95735 and http://stackoverflow.com/q/7264571/95735. -- ___ Python tracker rep...@bugs.python.org

[issue9148] os.execve puts process to background on windows

R. David Murray added the comment: This looks like the answer to the cygwin question, assuming things haven't changed: http://cygwin.com/ml/cygwin-developers/2001-02/msg00106.html Basically, it does the same thing as Python, except that a special return code is reported by the execing

[issue9148] os.execve puts process to background on windows

Eric Smith e...@trueblade.com added the comment: I believe it's true that Windows does not offer process replacement. I'm sure you could perform some tricks by essentially writing your own loader, but the practical answer is no. It might be worth looking into how cygwin implements exec().

[issue9148] os.execve puts process to background on windows

New submission from anatoly techtonik techto...@gmail.com: os.execve() is said to replace current process with new program. Unfortunately, when you try to call script that contains os.execve() on windows - that script spawns background process and control is immediately returned to the calling

[issue9148] os.execve puts process to background on windows

Amaury Forgeot d'Arc amaur...@gmail.com added the comment: on Windows, exec() does not really replace the current process. It creates a new process (with a new pid), and exits the current one. Hence the calling program only sees that the script has terminated. I don't see any easy solution on

[issue9148] os.execve puts process to background on windows

anatoly techtonik techto...@gmail.com added the comment: Does that mean that windows doesn't allow process replacement at all? I remember the time then game NoCD loaders were somehow able to load, patch and execute main program in their address space. --