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 Monson, Steven Noonan, dan, paul.moore, steve.dower, steven.downum, tim.golden, zach.ware
Date 2019-11-14.17:05:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I just added a PR that will produce ARM64 releases (as embeddable, nuget and Microsoft Store packages).

The only missing feature is tkinter (and everything that depends on it). For users who require that, I'd suggest grabbing the x86 installer from which works fine (apart from some minor arithmetic and process management bugs in the Windows emulation layer).

This is not saying we're going to release it just yet. Really it shouldn't be released until 3.9, as it's a new platform and we need to allow the 3rd party package ecosystem to catch up, but at least having the ability to build packages easily will enable those who are already trying to do it themselves.

Allegedly there's a lot of demand for Python on ARM64, but I haven't actually seen it other than this bug. And if that demand immediately extends to numpy or pywin32 on ARM64 then we're still a very long way from actually satisfying it.

I'll likely tweak the PR a bit more to prevent releasing ARM64 packages by default, but then I don't see any issue having it in the 3.8 and master branches for those who would be helped. Any thoughts/comments?
Date User Action Args
2019-11-14 17:05:50steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, steven.downum, Steven Noonan, Paul Monson, dan
2019-11-14 17:05:50steve.dowersetmessageid: <>
2019-11-14 17:05:50steve.dowerlinkissue33125 messages
2019-11-14 17:05:49steve.dowercreate