➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eryksun
Recipients Fredrik Mellbin, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-06-30.20:08:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561925288.32.0.474419941668.issue37452@roundup.psfhosted.org>
In-reply-to
Content 
> 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"?
History
Date User Action Args
2019-06-30 20:08:08eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, Fredrik Mellbin
2019-06-30 20:08:08eryksunsetmessageid: <1561925288.32.0.474419941668.issue37452@roundup.psfhosted.org>
2019-06-30 20:08:08eryksunlinkissue37452 messages
2019-06-30 20:08:08eryksuncreate