This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients paul.moore, steve.dower, tim.golden, zach.ware
Date 2022-01-28.16:52:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643388779.11.0.426548045355.issue46566@roundup.psfhosted.org>
In-reply-to
Content
We now have a traditional installer that runs on Windows ARM64 devices, but it omits the py.exe launcher. This is because sys.winver is "3.11-arm64" and hence the registry tag (see PEP 514) is not detected by the launcher.

Currently, the launcher is not included in the installer and appears as disabled with an explanatory note.

We need to add support for it eventually, and possibly block the final/RC/beta releases if we don't have it. (We don't ship the launcher with Nuget or Store packages, so nobody will miss it there, but they probably will here.)

32-bit apps can still run on ARM64, so it isn't essential to make it a native process. It just has to be able to detect the registry keys.

It should still support 32-bit and 64-bit installs, because those can also be run on ARM64 devices (though there are numerous things that don't work as well as a native build).

Possibly we want to just do the work to directly follow PEP 514 now? Depends on who volunteers to work on this, I guess.
History
Date User Action Args
2022-01-28 16:52:59steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware
2022-01-28 16:52:59steve.dowersetmessageid: <1643388779.11.0.426548045355.issue46566@roundup.psfhosted.org>
2022-01-28 16:52:59steve.dowerlinkissue46566 messages
2022-01-28 16:52:58steve.dowercreate