Accelerating the search for antimicrobial peptides with Google Antigravity
deepmind.google·2h ago
AI Engineering
Lobsters·2d ago·5 min read
A plea not to use uv-build
TL;DR
Gentoo users are urged to avoid using uv-build as a build backend due to its large size and portability issues, which outweigh its benefits. The Rust-based tool introduces significant overhead for building Python packages, complicating the development process.
✦ Why It Matters
Avoid using uv-build for Python packages to streamline builds and enhance portability on Gentoo.
Key Takeaways
- Reconsider using uv-build due to its large wheel size.
- Opt for smaller backends like flit-core for better efficiency.
- Be aware of portability issues with Rust-based tools.
- Minimize build times by avoiding frequent updates of uv-build.
Full Summary
The article expresses concern over the adoption of uv-build as a build backend for Python packages in Gentoo, highlighting its drawbacks. While uv-build is a Rust-based tool that offers some advantages, its wheel size ranges from 1.2 MiB to 1.5 MiB, making it a cumbersome dependency compared to smaller alternatives like flit-core, which is only 45 KiB.
Gentoo users face the challenge of frequently building uv-build from source, with 12 releases in just 30 days, leading to excessive build times. Portability is another major issue, as Rust's support across platforms is limited, and users may encounter bugs or memory constraints.
The article argues that the supposed performance benefits of uv-build are negligible, especially for regular users who primarily utilize pre-built wheels. Ultimately, the call is for developers to reconsider their reliance on uv-build in favor of more efficient and portable options.