[issue23462] All os.exec*e variants crash on Windows

Change by Steve Dower : -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue23462] All os.exec*e variants crash on Windows

Steve Dower added the comment: It's straightforward to detect path->narrow == NULL and raise instead of crashing. We can also trivially check path->wide on Windows and raise with a more specific error. Given it's already fixed for 3.6.0 and there's only one more binary release for 3.5 (and

[issue23462] All os.exec*e variants crash on Windows

STINNER Victor added the comment: > Just hit that bug. Is this really not yet fixed in any newer version? The bug was fixed in Python 3.6.0. It was fixed by Steve Dower in its implementation of the PEP 529, in the change e20c7d8a8187: -execv(path_char, argvlist); +#ifdef HAVE_WEXECV +

[issue23462] All os.exec*e variants crash on Windows

Andreas Bergmeier added the comment: Just hit that bug. Is this really not yet fixed in any newer version? -- nosy: +Andreas Bergmeier ___ Python tracker

[issue23462] All os.exec*e variants crash on Windows

eryksun added the comment: Calling nt.execv works with a unicode string because it creates a bytes path via PyUnicode_FSConverter. OTOH, nt.execve uses path_converter, which doesn't convert unicode to bytes on Windows. Thus in posixmodule.c, for the call execve(path-narrow, argvlist,

[issue23462] All os.exec*e variants crash on Windows

New submission from Jeremy Nicola: On Windows 7, using python 3.4.2 32 bits MSVCv.1600 or 3.4.1 64 bits, all the os.exec*e variants crash: os.execle('C:/Python34/python.exe','Python.exe','-V',{}) os.execve('C:/Python34/python.exe',['python.exe','-V'],{})

[issue23462] All os.exec*e variants crash on Windows

Jeremy Nicola added the comment: You should read: os.execv('C:/Python34/python.exe',['python.exe','-V']) os.execlp('C:/Python34/python.exe','python.exe','-V') os.execvp('C:/Python34/python.exe',['python.exe','-V']) for the what works. -- ___