Uv, a fast Python package and project manager

Original Article ↗ Hacker News Discussion ↗

A new Rust-based Python package and project manager called uv is winning over many developers with its speed, integrated handling of virtual environments and Python versions, and features like lockfiles and `uvx` for running tools in isolated environments. Supporters say it dramatically reduces friction compared to pip, Poetry, and Conda-based workflows, while skeptics worry about increased ecosystem fragmentation, reliance on unofficial Python builds, and the long‑term implications of a VC‑backed company controlling key developer tooling. Many expect uv to coexist with existing tools, with some calling for clearer guarantees around governance, standards alignment, and sustainability before fully committing.

Overall Reception & Performance

  • Many commenters report very positive experiences with uv: extremely fast installs, much quicker dependency resolution, and big reductions in build/release and CI times.
  • Some see this speed as mainly improving “flow” and reducing friction during development, not just deployment.
  • Others argue pip performance is “good enough” for their projects and don’t feel a strong need to switch.

Features & Workflow

  • Praised features include:
    • Simple commands for project setup (uv init, uv add, uv run).
    • Lockfile support and reproducible environments.
    • Automatic per-project .venv creation.
    • Python version management integrated with dependency management.
    • uvx for one-off tool execution (similar to npx/pipx).
  • Several users like that uv can coexist with conda (or be used under tools like pixi) and with existing standards like pyproject.toml.
  • Some prefer small, composable tools (pip + venv + separate helpers) and view “all-in-one project managers” as over-opinionated and brittle.

Compatibility & Ecosystem Fit

  • Reports of uv working transparently alongside pyenv/venv/pip when projects are standards-compliant.
  • Issues noted where uv-based changes in larger projects (e.g., Home Assistant) broke third-party extensions, highlighting backward-compat concerns.
  • Some worry about yet another tool adding to Python packaging fragmentation; others argue competition and specialization are healthy and that pip/setuptools have deep design flaws uv can sidestep.

Rust, Bootstrapping & Unofficial Builds

  • Tool being written in Rust is seen by many as a plus: easier distribution of fast single binaries, perceived safer implementation.
  • Critics worry:
    • Rust adds another ecosystem dependency to “basic Python”.
    • Fewer potential maintainers compared to pure-Python tools.
  • Use of unofficial standalone Python builds is contentious:
    • Supporters say official macOS builds aren’t suitable and that taking over portable builds is a net win.
    • Skeptics see risk if those third-party builds change or disappear.

VC Funding & Governance

  • Repeated concern about VC backing: fear of future paywalls, feature gating, or abandonment.
  • Others note:
    • The tools are open source and “forkable”.
    • The stated business model is to sell optional enterprise tools (e.g., private registries) around a free core.
  • Some express unease about a single company rapidly becoming highly influential in Python tooling; others see it simply as filling long-standing gaps.