[issue13792] The "os.execl" call doesn't give programs exit code

2012-06-29 Thread Tim Golden
Tim Golden added the comment: Closing as it's been pending for six months and I see nothing further to add -- stage: -> committed/rejected status: pending -> closed ___ Python tracker

[issue13792] The "os.execl" call doesn't give programs exit code

2012-01-17 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: No. On Windows the only way to start a new executable is to create a new process (with the CreateProcess function, which all spawn* and exec* functions ultimately call), and this yields a new PID. This is a fundamental difference with unix, where the onl

[issue13792] The "os.execl" call doesn't give programs exit code

2012-01-17 Thread Kay Hayen
Kay Hayen added the comment: Does the Python standard library not offer anything that does replace with current process code with another? I checked with subprocess, and admittedly it's not that. Does Win32 API offer nothing for that? -- ___ Python

Re: [issue13792] The "os.execl" call doesn't give programs exit code

2012-01-16 Thread Amaury Forgeot d'Arc
Le 16 janv. 2012 00:09, "Kay Hayen" a écrit : > I am the author of the Python compiler Nuitka. It has the ability to immediately execute the created executable file. For that I am using "os.execl" to immediately replace the compiler and run the freshly created binary instead. > > This worked well

[issue13792] The "os.execl" call doesn't give programs exit code

2012-01-15 Thread Kay Hayen
Kay Hayen added the comment: Well, I saw that code, but expected that there must be more to it. But I found out, the bug is actually caused by at least MinGW. See below how I build a program with it, that does "execl" on an error exiting program and then the "errorlevel" variable is "0", wher

[issue13792] The "os.execl" call doesn't give programs exit code

2012-01-15 Thread Antoine Pitrou
Antoine Pitrou added the comment: Python's os.execl simply calls Windows' execv() function, which AFAIK has nothing to do with cmd.exe. -- nosy: +brian.curtin, pitrou, tim.golden ___ Python tracker __

[issue13792] The "os.execl" call doesn't give programs exit code

2012-01-15 Thread Kay Hayen
New submission from Kay Hayen : Hello, I am the author of the Python compiler Nuitka. It has the ability to immediately execute the created executable file. For that I am using "os.execl" to immediately replace the compiler and run the freshly created binary instead. This worked well so far,