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

2019-08-17 Thread Steve Dower


Change by Steve Dower :


--
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-11 Thread Steve Dower


Steve Dower  added the comment:

Here's an example of someone hitting this issue: 
https://stackoverflow.com/q/56974927

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-07 Thread miss-islington


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


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-07 Thread Steve Dower


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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-07 Thread miss-islington


Change by miss-islington :


--
pull_requests: +14898
pull_request: https://github.com/python/cpython/pull/15166

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-07 Thread Steve Dower


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


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-07 Thread miss-islington


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)
https://github.com/python/cpython/commit/eab76c3c75a572566862200728cc8d05b3298f12


--
nosy: +miss-islington

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-07 Thread Steve Dower


Change by Steve Dower :


--
pull_requests: +14897
pull_request: https://github.com/python/cpython/pull/15165

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-07 Thread Steve Dower


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)
https://github.com/python/cpython/commit/1fab9cbfbaf19a7bc79cef382136fcf9491e3183


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-07 Thread miss-islington


Change by miss-islington :


--
pull_requests: +14895
pull_request: https://github.com/python/cpython/pull/15163

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-06 Thread Steve Dower


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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-08-06 Thread Steve Dower


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 the "core" executable be 
named differently between Python versions it'll fix a couple of minor issues.

Most importantly here, because the registry path would then point at 
"python3.8.exe" rather than "python.exe", it becomes more likely that the 
global alias will remain enabled and so launching via the registry path will 
work. The downside is that apps that use "$InstallPath\python.exe" rather than 
"$ExecutablePath" will not work. But the ExecutablePath value has been present 
for a while now, and PEP 514 specifies it as preferred when available, so I 
think that's okay.

We can also include a plain "python[w].exe" in the installation, but that'll 
only be useful for subprocess.run("python") from the same version - it won't be 
executable at all from outside the app package.

(None of this affects the regular installer, FWIW. That'll still be plain 
"python.exe".)

Anyone have any thoughts or concerns?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-07-31 Thread Steve Dower


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 only have to be installed for the 
current user. If they agree with that, we might get this fixed properly and 
then there's nothing to do here.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-07-31 Thread Jeremy Kloth


Change by Jeremy Kloth :


--
nosy: +jkloth

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2019-07-31 Thread Steve Dower


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 installing via the 
Store package points directly to the package install. There is no way to point 
at the local symlink.

I'm working with the Windows team to find either a fix or a workaround, but 
right now anyone who updates to preview Windows (or gets the update when it 
releases at the end of the year) will not be able to launch Python through 
tools that look in the registry.

--
assignee: steve.dower
components: Windows
messages: 348812
nosy: paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title: Registry keys for Windows Store package have wrong executable
type: behavior
versions: Python 3.8, Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com