[issue1576313] os.execvp[e] on win32 fails for current directory

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

[issue1576313] os.execvp[e] on win32 fails for current directory

Mark Lawrence added the comment: The patch deliberately says Windows msvcrt to distinguish it from the Python module of the same name. -- Added file: http://bugs.python.org/file35690/Issue1576313.diff ___ Python tracker rep...@bugs.python.org

[issue1576313] os.execvp[e] on win32 fails for current directory

Mark Lawrence added the comment: I'd intended to write a patch but got confused as msg51241 talks about execlp() in msvcrt but execlp is in the os module. Please advise. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org

[issue1576313] os.execvp[e] on win32 fails for current directory

R. David Murray added the comment: os.execlp *wraps* the interface of the same name in the platform C library. On Windows, that is execlp in the msvcrt[*]. On Linux, it is usually the execlp in glibc. [*] 'crt' stands for 'C runtime'. -- ___

[issue1576313] os.execvp[e] on win32 fails for current directory

anatoly techtonik techto...@gmail.com added the comment: There should be one uniform behavior on all platforms if Python is crossplatoform. As far as I can understand this issue - unix os.execv() requires ./ to be present to execute anything from current directory. On windows it is enough to

[issue1576313] os.execvp[e] on win32 fails for current directory

R. David Murray rdmur...@bitdance.com added the comment: The unix model should be followed (requiring an explicit reference to the current directory if it is not already in PATH), rather than the insecure Windows behavior, and this is indeed the current situation. The current behavior is