wheelgap tracker · Campaigns

Free-threaded Python 3.14 wheels on Linux x86_64 for the top 500

Free-threaded Python (3.14t) runs without the global interpreter lock, so threads can run Python code on several cores at once. A package with compiled code needs its own cp314t wheel for it; until it uploads one, everyone on 3.14t builds it from source, or can't install it at all. This page lists the packages among the 500 most-downloaded that ship a Linux x86_64 wheel for regular Python 3.14 but none for 3.14t. Publishing a cp314t wheel is taken as saying the package supports free-threading, so the thing to do is ask its maintainers whether that is planned, one package at a time, not send a build change.

Sources: docs.python.org/3/howto/free-threading-python.html · py-free-threading.github.io/

From the wheelgap 0.9.0 scan of 2026-11-21, using Python 3.14t (set by the campaign). As JSON: data/campaigns/ft-314-linux.json.

Coverage

95.4% of the top 500 packages have a Linux x86_64 wheel for Python 3.14t today (477 of 500).

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

Nightly scan totals for 3.14t linux-x86_64 since the campaign started on 2026-11-21. They count every package in the scan, not only this campaign's top N (history.json does not keep a top-N slice).

Nightly scan totals for 3.14t linux-x86_64
DateWheelsShare
2026-11-214,480 / 5,00089.6%

To do

20 of the top 500 packages have a Linux x86_64 wheel for Python 3.14 but not for free-threaded Python 3.14t, 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.

Free-threaded Python 3.14 wheels on Linux x86_64 for the top 500: packages to do, most-downloaded first
RankPackageStatus
92grpcio 1.85.3 · PyPIfrom source
146psycopg2-binary 2.9.13 · PyPIfrom source
152orjson 3.13.0 · PyPIfrom source
173zstandard 0.25.0 · PyPIfrom source
181psycopg-binary 3.3.9 · PyPI · has a notecan't install
195google-crc32c 1.9.0 · PyPIfrom source
210grpcio-tools 1.85.3 · PyPIfrom source
262pymupdf 2.1 · PyPIfrom source
283brotli 1.2.1 · PyPIfrom source
295litellm 1.110.2 · PyPIfrom source
313safetensors 0.8.0 · PyPIfrom source
319lz4 4.4.5 · PyPIfrom source
330pycryptodome 4.5.0 · PyPIfrom source
334fastuuid 0.14.0 · PyPIfrom source
366duckdb 2.0.1 · PyPIfrom source
376ruamel-yaml-clib 0.2.15 · PyPIfrom source
425polars-runtime-32 2.1.0 · PyPIfrom source
449opencv-python-headless 5.1.0.95 · PyPIfrom source
480tree-sitter 0.26.1 · PyPIfrom source
486ddtrace 4.17.2 · PyPIfrom source

Left out: 3 packages have no Linux x86_64 wheel for Python 3.14 either (psycopg2, backports-zstd, pyspark). Without a wheel for the regular build, a missing Python 3.14t wheel isn't a free-threading gap (an sdist-only release, or no Linux x86_64 wheels by design), so this campaign doesn't ask about it.

Done

0 of the 20 packages on the to-do list at the start (2026-11-21) now have a Linux x86_64 wheel for Python 3.14t.

The starting list is recorded in data/campaigns/ft-314-linux.json. 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.