[issue31074] Startup failure if executable is a \\?\ path on Windows

STINNER Victor added the comment: I got the same bug recently and I fixed it: commit dec39716ca93ee2e8d9b94915ece33014eb58e9e Author: Victor Stinner Date: Mon Sep 30 14:49:34 2019 +0200 bpo-38322: Fix gotlandmark() of PC/getpathp.c (GH-16489) Write the filename into a

[issue31074] Startup failure if executable is a \\?\ path on Windows

Shubha Ramani added the comment: May I take resolve this issue and submit a patch ? -- nosy: +shubha_bloodhound ___ Python tracker ___

[issue31074] Startup failure if executable is a \\?\ path on Windows

Steve Dower added the comment: Sounds like the right fix. We should increase the maximum path length though, since 3.6 and later can work with much longer paths on Win10 through normal APIs and without prefix. -- ___ Python tracker

[issue31074] Startup failure if executable is a \\?\ path on Windows

New submission from Eryk Sun: search_for_prefix in PC/getpathp.c sets the wrong path when Python is started with a \\?\ path on Windows, which results in the following crash: >>> subprocess.call(r'"\\?\C:\Program Files\Python36\python.exe"') Fatal Python error: Py_Initialize: unable to