<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/QbfTKOkwH" -->

---
title: A plea not to use uv-build | daily.dev
description: A Gentoo developer argues against using uv-build as a Python package build backend, citing its large size as a Rust-compiled binary (1.2-1.5 MiB wheels vs. 45...
canonical: https://daily.dev/posts/a-plea-not-to-use-uv-build-qbftkokwh
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: A plea not to use uv-build | daily.dev
og:description: A Gentoo developer argues against using uv-build as a Python package build backend, citing its large size as a Rust-compiled binary (1.2-1.5 MiB wheels vs. 45...
og:url: https://daily.dev/posts/a-plea-not-to-use-uv-build-qbftkokwh
og:image: https://api.daily.dev/og/posts/QbfTKOkwH.png
og:image:alt: A plea not to use uv-build
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# A plea not to use uv-build

**[Lobsters](https://daily.dev/sources/lobsters)** · 3 min read · 5 upvotes · 0 comments

## Summary

A Gentoo developer argues against using uv-build as a Python package build backend, citing its large size as a Rust-compiled binary (1.2-1.5 MiB wheels vs. 45 KiB for flit-core), frequent releases requiring repeated source builds on Gentoo, and portability problems on less common platforms (including bugs skipping SPARC support and address-space exhaustion on 32-bit systems). The author contends the claimed benefits of consistency with uv and performance gains (around 100ms) don't outweigh these costs, especially since source distribution builders and packagers bear the brunt while regular users rely on prebuilt wheels anyway.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blogs.gentoo.org/mgorny/2026/10/12/a-plea-not-to-use-uv-build>

## Questions this post answers

### Why do some developers recommend avoiding uv-build as a Python package build backend?

Because uv-build is a large Rust-compiled binary with wheels between 1.2 and 1.5 MiB, compared to 45 KiB for flit-core, and it releases very frequently (12 releases in 30 days), forcing source-based distributions like Gentoo to rebuild it constantly. It also has portability problems on less common platforms, including bugs skipping SPARC support and address-space exhaustion when building on 32-bit systems.

_Weigh these packaging trade-offs by following Python tooling debates like this on daily.dev._

### Does switching a Python project's build backend to uv-build actually improve build performance?

Any performance gain is minimal, realistically around 100 milliseconds, and applies only to project developers, CI/CD workflows, packagers, and users building from source distributions, since regular users install prebuilt wheels instead. That small gain can be offset by the time needed to download the larger uv-build wheel or build it from source.

_Developers deciding between python build backends can track this kind of analysis on daily.dev._

### Can I use flit-core or hatchling as a build backend instead of uv-build while still using uv as my package manager?

Yes, because PEP 517 allows any build backend to work with any frontend tool. A project can use flit-core or hatchling as its build backend and still be installed, built, or managed with uv, pip, or any other PEP 517-compliant frontend without losing compatibility.

_Follow packaging standards discussions like this on daily.dev when choosing python build tooling._

## Community take

How the wider developer community reacted, aggregated from 2 discussions and 169 comments across hackernews, lobsters (as of 2026-10-13).

**TL;DR:** Discussion largely centers on whether Gentoo's complaint about uv-build's frequent rebuilds is really uv's fault or a self-inflicted consequence of Gentoo's rolling-release, build-from-source model, with a uv maintainer pushing back that semver version bounds already solve most of the problem.

**Sentiment:** 25% positive · 45% mixed · 30% skeptical

**The case for**

- A uv maintainer explained that projects can use semver ranges for the build backend so Gentoo wouldn't need to rebuild on every patch release.
- Some argued that distros already patch build processes routinely, so adapting to a less-frequent update policy for uv-build should be feasible.
- Several noted Rust-based tooling in the Python ecosystem is increasingly inevitable given upcoming Rust use in CPython itself, so complaints about rustification may be fighting a losing battle.

**The pushback**

- Many pointed out that if a project doesn't pin an exact version, Gentoo's source-rebuild model still forces a rebuild whenever any compatible uv-build version is released, since the backend is treated as a dependency.
- Some felt the standardization argument is overstated since different build backends accept different, incompatible pyproject.toml configurations, making swapping backends non-trivial.
- Others were skeptical that supporting obscure platforms like SPARC or HP-UX is worth the burden on maintainers, while some countered that marginalizing niche platform users sets a bad precedent.
- A few questioned relying on a corporate-backed tool (uv) as critical ecosystem infrastructure given it lacks the broader governance of projects like Python or PostgreSQL.

**By community**

- hackernews (heated): A long, contentious back-and-forth between a uv maintainer and Gentoo sympathizers about whether semver bounds actually solve the rebuild problem, alongside tangential debates about Gentoo's purpose and Rust creeping into Python/CPython.
- lobsters (mixed): More measured exchange featuring the same uv maintainer clarifying intentions, with some agreement that Gentoo's own policies contribute to the pain and some sympathy for the original complaint.

**Hottest debate:** Whether the rebuild burden is inherent to uv-build's release cadence or is actually a self-inflicted problem from how Gentoo (and projects that don't pin backend versions) handle build-dependency tracking.

**Open questions**

- Would clearer official guidance from uv on safe update cadence for uv-build actually change how often Gentoo rebuilds it in practice?
- How many projects using uv-build as a backend actually pin exact versions versus using the default semver range?
- Will a future pure-Python fallback for uv-build (as suggested by one commenter) materialize to address platforms where the Rust binary can't be built?

**Highlights**

> > The nice thing about Python packaging is that it’s standardized But it isn't. Once upon a time, it was: you used distutils. But of course distutils had a lot of problems. Instead of adopting a single standardized solution for those problems, the Python developers punted and let third parties do it. So now we do not have a single standardized solution for building Python packages; we have a bunch of third party solutions, none of which is in the Python standard library. Yes, all those third party solutions have to be PEP 517 compatible, but that's not standardization on a tool; it's just standardization on an interface between the backend and the frontend. Which is nice, but doesn't solve the problem under discussion here. > if uv’s build backend doesn’t fit into the hole you want, then you can use any number of other backends that do an admirable job of conforming to the packaging standards. As the project developer, sure. But as a Linux distro building your python package, Gentoo has to use the build backend you specify. It can't say, well, this particular package is just pure python, so really all we need is a minimal tool to build a pure python none-any wheel. It has to use the backend you specified. > I don’t understand why Gentoo needs to rebuild every single release of uv-build. Because if you don't pin a version of uv-build in your project, that means "use the latest version available". Gentoo can't second guess you--even if it were able to verify somehow that the new version of uv-build that just got released will end up producing an identical wheel for your project as the previous version, without actually using the new version of uv-build. > you can do a normal version bound in your Python build backend metadata Sure, but how many users of uv-build actually do that? Seems like the answer to that is "not enough to matter".
> — [pdonis on hackernews · 2 comments](https://news.ycombinator.com/item?id=50077466)

> Gentoo builds every package from source on every user's machine, and when each user does an update, every package that changed gets rebuilt from source again. So every Gentoo user that has a Python project that uses uv-build ends up having to rebuild uv-build, and then every Python project they have that uses it, every time uv-build pushes an update. Other distros don't necessarily have quite the same problem because, if they include packages of Python projects, they don't normally track the build backend as a dependency. So if uv-build pushes an update, the distro would push an updated package for uv-build, but they wouldn't look at every Python project they package to see if it used uv-build as a build backend and rebuild it if it did. It's the "rebuild from source every time" aspect of Gentoo that forces that connection.
> — [pdonis on hackernews · 3 comments](https://news.ycombinator.com/item?id=50077866)

> > they don't normally track the build backend as a dependency... It's the "rebuild from source every time" aspect of Gentoo that forces that connection I don't follow. This feels like Gentoo is mishandling build-tool dependencies. Does Gentoo also recompile every C/C++ library in the dependency tree every time GCC pushes a minor version bump?
> — [swiftcoder on hackernews · 5 comments](https://news.ycombinator.com/item?id=50078068)

> Personally, I'm against integrating anything backed by corporate interest as a central dependency for an ecosystem. It should be self-supporting, as the interests of the company can and will change at any time, rather than being organised specifically to support the ecosystem as a whole.
> — [addison on lobsters · 3 points, 1 comments](https://lobste.rs/s/73ssw1/plea_not_use_uv_build#c_efm1ve)

> It would be nice if there was a pure python fallback for uv-build. There are definitely some situations where it's not possible to use the uv build backend today (micropip for instance).
> — [mitsuhiko on lobsters · 4 points](https://lobste.rs/s/73ssw1/plea_not_use_uv_build#c_jev7h3)

**Source threads**

- [hackernews](https://news.ycombinator.com/item?id=50076048) · 57 points · 154 comments
- [lobsters](https://lobste.rs/s/73ssw1/plea_not_use_uv_build) · 52 points · 15 comments

## Similar posts on daily.dev

- [How uv got so fast](https://daily.dev/posts/how-uv-got-so-fast-fgscee8dp) · Hacker News · 5 upvotes · 2 comments
- [uv is fantastic, but its package management UX is a mess](https://daily.dev/posts/uv-is-fantastic-but-its-package-management-ux-is-a-mess-dvqxsrkx0) · Planet Python · 0 upvotes · 0 comments

---

Tags: [#python](https://daily.dev/tags/python), [#rust](https://daily.dev/tags/rust)

[View this post on daily.dev](https://daily.dev/posts/a-plea-not-to-use-uv-build-qbftkokwh)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"A plea not to use uv-build","url":"https://daily.dev/posts/a-plea-not-to-use-uv-build-qbftkokwh","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/a-plea-not-to-use-uv-build-qbftkokwh"},"datePublished":"2026-10-13T16:59:06.619Z","dateModified":"2026-10-13T21:43:23.401Z","description":"A Gentoo developer argues against using uv-build as a Python package build backend, citing its large size as a Rust-compiled binary (1.2-1.5 MiB wheels vs. 45...","image":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","thumbnailUrl":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/a-plea-not-to-use-uv-build-qbftkokwh","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"python,rust","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"A plea not to use uv-build"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/a-plea-not-to-use-uv-build-qbftkokwh#faq","mainEntity":[{"@type":"Question","name":"Why do some developers recommend avoiding uv-build as a Python package build backend?","acceptedAnswer":{"@type":"Answer","text":"Because uv-build is a large Rust-compiled binary with wheels between 1.2 and 1.5 MiB, compared to 45 KiB for flit-core, and it releases very frequently (12 releases in 30 days), forcing source-based distributions like Gentoo to rebuild it constantly. It also has portability problems on less common platforms, including bugs skipping SPARC support and address-space exhaustion when building on 32-bit systems. Weigh these packaging trade-offs by following Python tooling debates like this on daily.dev."}},{"@type":"Question","name":"Does switching a Python project's build backend to uv-build actually improve build performance?","acceptedAnswer":{"@type":"Answer","text":"Any performance gain is minimal, realistically around 100 milliseconds, and applies only to project developers, CI/CD workflows, packagers, and users building from source distributions, since regular users install prebuilt wheels instead. That small gain can be offset by the time needed to download the larger uv-build wheel or build it from source. Developers deciding between python build backends can track this kind of analysis on daily.dev."}},{"@type":"Question","name":"Can I use flit-core or hatchling as a build backend instead of uv-build while still using uv as my package manager?","acceptedAnswer":{"@type":"Answer","text":"Yes, because PEP 517 allows any build backend to work with any frontend tool. A project can use flit-core or hatchling as its build backend and still be installed, built, or managed with uv, pip, or any other PEP 517-compliant frontend without losing compatibility. Follow packaging standards discussions like this on daily.dev when choosing python build tooling."}}]}
```

