Author steve.dower
Recipients paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-07-31.16:20:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1564590002.03.0.889517252351.issue37734@roundup.psfhosted.org>
In-reply-to
Content
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.
History
Date User Action Args
2019-07-31 16:20:02steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware
2019-07-31 16:20:02steve.dowersetmessageid: <1564590002.03.0.889517252351.issue37734@roundup.psfhosted.org>
2019-07-31 16:20:01steve.dowerlinkissue37734 messages
2019-07-31 16:20:01steve.dowercreate