Eryk Sun <eryk...@gmail.com> added the comment:
> The expected behavior would be to have it point to > "%LOCALAPPDATA%\Microsoft\WindowsApps\Python37.exe" (or something > else that's reasonable) since PEP514 requires it to be an actual > executable. This appears to be a duplicate of issue 36649. But I think this has to be looked at again. In Windows 10 1903 (build 10.0.18362.*), CreateProcess can directly run the real executable that's installed under "%ProgramFiles%\WindowsApps" by getting the package information it needs from the user's corresponding app-exec link in "%LocalAppData%\Microsoft\WindowsApps". Apparently the latest skip-ahead preview releases no longer implement this, in which case shouldn't the installer set the ExecutablePath and WindowedExecutablePath values to the user's "python.exe" and "pythonw.exe" app-exec links in "%LocalAppData%\Microsoft\WindowsApps"? ---------- nosy: +eryksun _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37452> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
