GoKawiilGentoo developer urges Python package maintainers to avoid uv-build backend
A Gentoo contributor is publicly asking Python package maintainers not to adopt uv-build as their build backend, citing damage to Gentoo package support when key dependencies switch to it. The post clarifies it's not a criticism of uv or Astral's other tools generally, but specifically objects to uv-build's size, its Rust implementation, and its frequent release cadence.
GoKawiil's interpretation of the reporting above, not reported fact.
The plea highlights friction between fast-moving Rust-based Python tooling and source-based distributions like Gentoo, which must compile every dependency from scratch for every release. If more projects adopt uv-build, Gentoo users could face longer build times and lost architecture support, since Rust's platform coverage lags behind pure Python or C-based toolchains on niche systems like SPARC.
- A Gentoo developer is asking maintainers to avoid uv-build due to its impact on source-based distros.
- uv-build is criticized for being a large Rust binary with frequent releases compared to lightweight pure-Python alternatives like flit-core.
- Portability concerns are raised, including Rust's narrower platform support and toolchain issues on architectures like SPARC.
Source: blogs.gentoo.org, 2026-10-13
Published there as: “A plea not to use uv-build”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.