Steve Dower added the comment:
> The store app doesn't add "App Paths" entries for "python.exe" and
> "python3.exe".
You're right, it's not following the aliases, but the actual executable. For
3.7, we had them as "python.exe", but from 3.8 they became "python3.8.exe" with
a "python.exe"
Eryk Sun added the comment:
> IMO, this makes it the 'system' Python.
"App Paths" entries can be used like versioned symlinks in POSIX. For example,
an "App Paths" entry for "python3.exe" can refer to a particular installation's
"python.exe". That said, "App Paths" is only used by the shell
Steve Dower added the comment:
Somewhat deliberate. We moved to properly support side-by-side installs, which
can't be done with this key - App Paths would end up out of sync with PATH...
almost instantly, really. (However, the Windows Store package manages this
correctly in line with its
