Python Windows on Arm ecosystem report

[Grant Likely]

Hi Marcus

From the call yesterday I pulled together a tool that generates an ecosystem report. Is this the sort of data you’re looking for? This is for the top 1000 packages. It is easy to adapt the search criteria from here and also dig into more details on the blockers.

Everything here is based on public data. It isn’t an exhaustive search.

https://claude.ai/artifact/KiRoGa9rGDtwMKTggsaWYc

Grant

-- 

Grant Likely

Arm Fellow and CoreCollective Technical Chair

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[Marcus Perryman]

+Gleb

This looks good, thx Grant.

Could we run this periodically to get a track of the direction things are going?

[Nathalie Chan King Choy]

Hi Grant,

Does your report include awareness of data in these trackers created by Gleb & Omair, or are you going direct from projects?

https://github.com/khmyznikov/PyEnv-WoA-State/issues/1

https://omjavaid.github.io/wheels-on-arm/

Thanks & regards,

Nathalie

[Nathalie Chan King Choy]

[resending with my corecollective email so that reply makes it to the list + into the discussion archive]

Hi Grant,

Does your report include awareness of data in these trackers created by Gleb & Omair, or are you going direct from projects?

https://github.com/khmyznikov/PyEnv-WoA-State/issues/1

https://omjavaid.github.io/wheels-on-arm/

Thanks & regards,

Nathalie

On Wed, 21 Oct 2026 at 11:18, Marcus Perryman <Marcus....@microsoft.com> wrote:

[Mayank Agrawal]

Hi Grant,

Thank you for putting together the Windows on ARM Python Ecosystem Report. Apologies for missing this week's call.

I went through the report (21-Oct) and compared it against our tracker. A few blocked libraries in the report are captured in our tracker as well. Below are the packages where QC already has work in progress -  

1. Packages where we already have an open PR or active work (needs maintainer traction)

Package	PR / work	Status
pyarrow	apache/arrow #48539	Waiting on the abi3 work; maintainers short of review time
tiktoken	openai/tiktoken #501	Open; no maintainer response since March
confluent-kafka	confluent-kafka-python #2190	Open; CLA signed, no review yet
opencv-python(-headless)	opencv-python #1143	Planned for OpenCV 5.0; under discussion with maintainers.
setproctitle	py-setproctitle #164	Open; no response
dbt-extractor	dbt-labs/dbt-extractor #142	Open, no reviews
fastuuid	fastuuid/fastuuid #63	Open; no reviews
google-crc32c	google/crc32c #73 (approved, not merged)	Wheel request now at google-cloud-python #16516
torch / torchvision	PyTorch perf PRs + benchmarks	We are trying to establish communication with Meta.
temporalio	Working wheel built on fork CI	Blocked on cryptography wheels
jpype1	Builds locally	Blocked on Azure Pipelines having no Windows ARM64 agents

2. Packages where we can support by opening PRs

• PyMuPDF: ARM64 wheels shipped in 1.28.2 but were dropped in 2.0. We can raise an issue/PR to restore them.
• pyyaml, snowflake-connector-python: ARM64 wheels are missing only for some Python versions; small CI PRs should cover them.
• fonttools, chardet, isort, pytokens, dulwich, simplejson, magika: candidates for small CI PRs (We can work on these and add support for CI if required)

3. Blocked: we cannot progress without maintainer/vendor support

• brotli: Python wheels are built in google/brotli-wheels, which has no ARM64 entry, and the maintainer is unresponsive.
• cryptography (fixed, waiting for the 51.0 release) and lightgbm (fixed, no release since July): these block our PyArrow tests, Optuna, Pyrit and yasa.
• debugpy and awscrt: need an ARM64 build agent in Microsoft's and AWS's internal release pipelines respectively.

Thanks & Regards,

Mayank Agrawal

---

From: Nathalie Chan King Choy <nath...@corecollective.dev>
Sent: Wednesday, October 21, 2026 11:57 PM
To: Marcus Perryman <Marcus....@microsoft.com>
Cc: Grant Likely <Grant....@arm.com>; CoreCollective Windows on Arm <windows...@corecollective.dev>; Gleb Khmyznikov <gleb.kh...@microsoft.com>
Subject: [CoreCollective WoA] Re: Python Windows on Arm ecosystem report

 

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

--
You received this message because you are subscribed to the Google Groups "(Deprecated) CoreCollective Windows on Arm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to windows-on-ar...@corecollective.dev.
To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/windows-on-arm/CAJ-KXzrZmicT_Vnps7TKx3eX0OTDo0Pn_HwoNNYF4rgXbWUzdg%40mail.gmail.com.

[Grant Likely]

No, the tracker isn’t pulling anything from Gleb & Omair’s tracker, but that can be changed or it be merged in. I certainly don’t want to create competing trackers! This was created via a few hours of quality time with an AI assistant. It is designed to be run periodically. I’ve not pushed it out to Github or anywhere else yet where it could be done with a regular CI job.

Gleb, how is your tracker being kept up to date? I can see that there is some testing performed.  The report I posted only covers availability of wheels for the top 1000 packages. It doesn’t do any testing. The package status bit looks like I’ve duplicated work, but the research on reasons why could be integrated in.

g.

[Rajath Vishwanath Holla]

Nvidia CUDA wheels are already published on PyPI. The cu12 wheels in the list have been updated as WinARM64 is supported on CUDA 13.4 and later. The rest of the features are Linux only and hence we don't have the wheels for them. 

Rajath

---

From: Grant Likely <Grant....@arm.com>
Sent: Thursday, October 22, 2026 9:15 AM
To: Nathalie Chan King Choy <nathal...@linaro.org>; Marcus Perryman <marcus....@microsoft.com>
Cc: CoreCollective Windows on Arm <windows...@corecollective.dev>; Gleb Khmyznikov <gkhmy...@microsoft.com>
Subject: [CoreCollective WoA] Re: Python Windows on Arm ecosystem report

 

You don't often get email from grant....@arm.com. Learn why this is important

External email: Use caution opening links or attachments

--
You received this message because you are subscribed to the Google Groups "(Deprecated) CoreCollective Windows on Arm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to windows-on-ar...@corecollective.dev.

To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/windows-on-arm/AM0PR08MB1128170F56E42904A6C1006D195652%40AM0PR08MB11281.eurprd08.prod.outlook.com.