[issue37734] Registry keys for Windows Store package have wrong executable

Change by Steve Dower : -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue37734] Registry keys for Windows Store package have wrong executable

Steve Dower added the comment: Here's an example of someone hitting this issue: https://stackoverflow.com/q/56974927 -- ___ Python tracker ___

[issue37734] Registry keys for Windows Store package have wrong executable

miss-islington added the comment: New changeset 84d31bbf1f7e10bde1ceadcfa0d83d30a04313d5 by Miss Islington (bot) in branch '3.8': bpo-37734: Remove unnecessary brace escapes in PC/layout script (GH-15165) https://github.com/python/cpython/commit/84d31bbf1f7e10bde1ceadcfa0d83d30a04313d5

[issue37734] Registry keys for Windows Store package have wrong executable

Steve Dower added the comment: Going to leave this open in commit review for now. I believe this will significantly improve the reliability, but depending on which Windows bugs people run into there may still be more things we can do. -- stage: patch review -> commit review

[issue37734] Registry keys for Windows Store package have wrong executable

Change by miss-islington : -- pull_requests: +14898 pull_request: https://github.com/python/cpython/pull/15166 ___ Python tracker ___

[issue37734] Registry keys for Windows Store package have wrong executable

Steve Dower added the comment: New changeset 0378d98678f3617fd44d9a6266e7c17ebce62755 by Steve Dower in branch 'master': bpo-37734: Remove unnecessary brace escapes in PC/layout script (GH-15165) https://github.com/python/cpython/commit/0378d98678f3617fd44d9a6266e7c17ebce62755 --

[issue37734] Registry keys for Windows Store package have wrong executable

miss-islington added the comment: New changeset eab76c3c75a572566862200728cc8d05b3298f12 by Miss Islington (bot) in branch '3.8': bpo-37734: Fix use of registry values to launch Python from Microsoft Store app (GH-15146)

[issue37734] Registry keys for Windows Store package have wrong executable

Change by Steve Dower : -- pull_requests: +14897 pull_request: https://github.com/python/cpython/pull/15165 ___ Python tracker ___

[issue37734] Registry keys for Windows Store package have wrong executable

Steve Dower added the comment: New changeset 1fab9cbfbaf19a7bc79cef382136fcf9491e3183 by Steve Dower in branch 'master': bpo-37734: Fix use of registry values to launch Python from Microsoft Store app (GH-15146)

[issue37734] Registry keys for Windows Store package have wrong executable

Change by miss-islington : -- pull_requests: +14895 pull_request: https://github.com/python/cpython/pull/15163 ___ Python tracker ___

[issue37734] Registry keys for Windows Store package have wrong executable

Change by Steve Dower : -- keywords: +patch pull_requests: +14882 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/15146 ___ Python tracker

[issue37734] Registry keys for Windows Store package have wrong executable

Steve Dower added the comment: It looks like the best solution here may be to rename the bundled executables to "python3.8.exe" etc. rather than "python.exe". We will still keep the "python.exe" alias, and sys.executable won't change (it'll still point to the stable alias), but by having

[issue37734] Registry keys for Windows Store package have wrong executable

Steve Dower added the comment: So far we've figured out that using the full installed path will work fine (by design) if you have enabled the matching alias. So essentially, if Python is on your PATH, you can also launch it using the full path. I'm trying to convince them that it should

[issue37734] Registry keys for Windows Store package have wrong executable

Change by Jeremy Kloth : -- nosy: +jkloth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37734] Registry keys for Windows Store package have wrong executable

New submission from Steve Dower : The next update to Windows will prevent launching executables from within the package install folder, and require you to launch from the user's local symlink to the executable (see issue37369). Currently, the only value we can put into the registry when