wheelgap tracker · Campaigns

musllinux aarch64 wheels for the top 500

musllinux aarch64 is what pip installs from in python:*-alpine images on ARM64 hosts such as AWS Graviton, Ampere and Apple-silicon machines running Docker. This page turns the gaps among the most-downloaded packages into a list people can work through, one package at a time.

From the wheelgap 0.9.0 scan of 2026-11-16, using Python 3.14 (set by the campaign). As JSON: data/campaigns/musl-aarch64.json.

Coverage

95.6% of the top 500 packages have an Alpine ARM64 wheel today (478 of 500).

Pure-Python packages have a wheel for every platform, so that share flatters it. Of the 84 with compiled code, 73.8% have one (62 of 84).

Nightly scan totals for 3.14 musl-aarch64 since the campaign started on 2026-11-11. They count every package in the scan, not only this campaign's top N (history.json does not keep a top-N slice). A night marked with a wheelgap version is the first scan with that release: its change from the night before can come from the tool (new targets, or different rules for which wheels count), not only from packages shipping wheels.

DateWheelsShareNote
2026-11-114,388 / 5,00087.8%
2026-11-124,388 / 5,00087.8%
2026-11-134,388 / 5,00087.8%wheelgap 0.9.0
2026-11-144,390 / 5,00087.8%
2026-11-154,390 / 5,00087.8%
2026-11-164,391 / 5,00087.8%

To do

19 of the top 500 packages have Python 3.14 wheels for other platforms but not Alpine ARM64, most-downloaded first. A package with a note links it: read the note first. Pick one package, not a list. Search its issue tracker first: someone may have asked already. If nobody has, open one issue there that links the package's page on this tracker and says which wheel is missing, and wait for a maintainer to agree before sending a pull request. Never file the same request across many projects at once, and take "not now" for an answer. How to ask for a missing wheel.

RankPackageStatus
155scikit-learn 1.9.1 · PyPIfrom source
172matplotlib 3.11.2 · PyPIfrom source
195google-crc32c 1.9.0 · PyPIfrom source
253playwright 1.65.2 · PyPIfrom source
262pymupdf 2.1 · PyPIfrom source
275snowflake-connector-python 5.2.0 · PyPIfrom source
285onnxruntime 1.32.0 · PyPIcan't install
289watchdog 7.1.0 · PyPIfrom source
319lz4 4.4.5 · PyPIfrom source
362pymongo 4.20.0 · PyPIfrom source
366duckdb 2.0.0 · PyPIfrom source
386llvmlite 0.50.0 · PyPIfrom source
387numba 0.68.1 · PyPIfrom source
397torch 2.15.0 · PyPIcan't install
427zope-interface 8.7 · PyPIfrom source
449opencv-python-headless 5.0.0.93 · PyPI · has a notefrom source
473triton 3.9.0 · PyPIcan't install
480tree-sitter 0.26.1 · PyPIfrom source
494confluent-kafka 2.16.1 · PyPIfrom source

Left out: 3 packages have no Python 3.14 wheel for any Linux platform yet (psycopg2, backports-zstd, pyspark). That's a gap for the project as a whole (a new Python, an sdist-only release, or no Linux wheels by design), not one this campaign should ask about.

Done

0 of the 19 packages on the to-do list at the start (2026-11-11) now have an Alpine ARM64 wheel.

The starting list in data/campaigns/musl-aarch64.json was reconstructed on 2026-11-12 from that night's to-do list and the change log since the start. A package that gained the wheel and lost it again isn't counted, and To do can include packages that weren't on the list at the start (new to the top), which don't count here either. Dates are from the nightly change log, which keeps the last 90 days and skips nights when the scan moved to a new wheelgap version. Was is the status at the start.

None yet.