Commenters debated whether uv-build is a reasonable upstream choice or a burden for source-focused distros like Gentoo. uv maintainer woodruffw argued uv-build follows packaging standards and suggested Gentoo could avoid rebuilding every patch release (proposing slower update cadence or version bounds), noting frequent uv-build releases mainly track internal uv changes. Others pushed back: afdbcreid and the__alchemist said users and volunteers may legitimately prefer binary wheels and Gentoo shouldn’t dictate their tooling; throwawayy6767 and similar voices urged acceptance of binaries. pdonis countered that Python packaging isn’t a single standardized tool - only an interface - so distros must honor whatever build-backend a project declares, and many projects don’t pin uv-build versions, which forces rebuilds. amluto proposed a reproducible pure-Python wheel model to sidestep tool differences.
Technical and cultural divides surfaced around portability, CI cost, and platform support. Commenters like the8472 and shadowgovt discussed compile-time tradeoffs (LTO, optimization levels) and download vs build time in CI; Cyph0n suggested caching binary artifacts; nimish, doctorpangloss and others raised legitimate concerns about exotic platforms (SPARC, mainframes) that may lack uv-build binaries. Proposals ranged from rewriting uv-build in portable C to distro-side patching; opinions split between maintaining upstream flexibility and insisting on distro-friendly source-buildability.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.