-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
py.exe cannot locate Store package #82314
Comments
The py.exe launcher cannot locate installations from the Store (unless you have no other installations on your machine, which is unlikely). |
I added an "exe_display" override for listing paths, since the full path to the store app is not supposed to be used by users (it's different from sys.executable) and is only going to work when the shorter name is on PATH anyway (due to a limitation in Windows that I'm still trying to get fixed). I also enabled support for the ExecutablePath key, which has the added benefit of making the debug py_d.exe able to find release Python 3.5+ installs (as well as finding the Store install at all, which is now using python3.8.exe as the main file because of the limitation I mentioned above). |
Sample output after this change (some paths elided): Installed Pythons found by ...\py.exe Launcher for Windows |
MAX_VERSION_SIZE was increased, so the INSTALLED_PYTHON version string is now the full registry key name with the "-32" suffix. If that's intentional, you'll have to account for it in show_python_list. But I don't think the "-32" suffix belongs in the version string. |
Ah, good catch, I didn't notice that. Because those are special cases, we should strip it off the version string. One day when we implement PEP-514 properly then they'll come back (and we'll probably drop the -64 suffix for consistency with the PEP). |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: