Hacker News: zanie

New comment by zanie in "Uv 0.12.0"

zanie — Tue, 28 Jul 2026 21:46:44 +0000

Yes! It's in progress — it's already there, just hidden as we iterate on it.

(but as a note, the initial `uv lock` will already attempt to choose the highest possible versions and `uv lock --upgrade` will do so again, requests for `uv upgrade` are generally centered around changing the constraints in the `pyproject.toml`)

New comment by zanie in "Uv 0.12.0"

zanie — Tue, 28 Jul 2026 20:38:14 +0000

It makes `uv run ` work by default, I expect most projects to need an entry point.

New comment by zanie in "Uv 0.12.0"

zanie — Tue, 28 Jul 2026 20:33:28 +0000

So far the maintenance burden has been quite bearable and extending pip provides us with an opportunity to explore and encourage improvements upstream which are still beneficial to a lot of people.

New comment by zanie in "Uv 0.12.0"

zanie — Tue, 28 Jul 2026 20:31:12 +0000

I hadn't considered that, it's an interesting idea. We generally hold a very high bar for nagging users or gating behaviors. It's possible we'll reach a point someday where this is appropriate! I think you're right that we need to teach people better workflows, but that's happening organically as use of the tool grows and people's first exposure to a Python project is `uv init` and `uv add` rather than `pip`.

New comment by zanie in "Uv 0.12.0"

zanie — Tue, 28 Jul 2026 20:25:18 +0000

Unfortunately dynamic metadata is not efficient for package resolution, so we don't want to encourage it. Instead, we want to design a better workflow for using source control for versioning, but haven't had the time to do so.

New comment by zanie in "Uv 0.12.0"

zanie — Tue, 28 Jul 2026 20:23:36 +0000

Pixi is very focused on the Conda ecosystem and implements a sort of bridge across the Conda and PyPI ecosystems. I am very interested in solving the problems that motivated creation of the Conda ecosystem, but I want to do so by driving forward the PyPI ecosystem so those use-cases can be addressed in _many_ tools instead of just one. This is the main reason you don't see us pursuing Conda package support in uv directly (in the style of Pixi).

There have been several threads about us collaborating or converging, but there are no concrete plans to do so at this time. We share some Rust crates, e.g., Pixi uses our internals to solve the PyPI-side of their dependencies, and we occasionally fix or change things for each other.

New comment by zanie in "Uv 0.12.0"

zanie — Tue, 28 Jul 2026 20:17:48 +0000

Yes! We've been working on this for quite some time as it's one of the worst experiences in Python packaging today.

There are two PEPs that we're involved with that will provide the components for the ecosystem to properly declare metadata in this domain [1] [2].

We're also working on some features in uv, such as the torch backend option [3], to improve the situation in the interim.

We'll be announcing more in this area in the near future!

[1] https://peps.python.org/pep-0817/ [2] https://peps.python.org/pep-0825/ [3] https://docs.astral.sh/uv/guides/integration/pytorch/#automa...

New comment by zanie in "Uv 0.12.0"

zanie — Tue, 28 Jul 2026 20:11:50 +0000

I think we're doing what we should making isolated environments easy to use. I don't think we should take options away from people that need them.

New comment by zanie in "Uv 0.12.0"

zanie — Tue, 28 Jul 2026 20:10:10 +0000

We have the interface because we care a lot about meeting people where they are.

We keep the interface because we care a lot about long-term support and compatibility. I cannot imagine removing it.

We generally want to add features to the top-level interface such that people don't need or want to use the pip-interface because the top-level interface does everything you need, but better.

New comment by zanie in "Uv is fantastic, but its package management UX is a mess"

zanie — Fri, 22 May 2026 04:26:34 +0000

I don't think it's true at all that "dropping features" makes uv fast. As an author of uv, I think that particular section of the article is way off base.

New comment by zanie in "Uv is fantastic, but its package management UX is a mess"

zanie — Fri, 22 May 2026 04:17:05 +0000

(I work on uv)

As a note, you can set the default bounds for `uv add` in persistent configuration — no need to provide it every time. See https://docs.astral.sh/uv/reference/settings/#add-bounds

We prefer not to add upper bounds by default because it causes a lot of unnecessary conflicts in the ecosystem. I previously collected some resources on this back when I used Poetry :) see https://github.com/zanieb/poetry-relax#references

New comment by zanie in "Uv is fantastic, but its package management UX is a mess"

zanie — Fri, 22 May 2026 04:13:20 +0000

I'm a bit confused, `uv run --with $package main --help` should do what you say with very little overhead. We won't reinstall it every time, `--with` environments are stored in the cache and retained. Even if the environment is cached, the dependency is cached and installing from the cache is very fast (<200ms for sure).

Please feel free to open a reproduction with details and we can look into it.

(I work on uv)

New comment by zanie in "Uv is fantastic, but its package management UX is a mess"

zanie — Fri, 22 May 2026 04:09:52 +0000

fwiw `uv upgrade` is on the roadmap — we just haven't done it yet because it's hard to build a great experience for it (there are far more nuances than people expect) and we're a small team with a lot of priorities.

New comment by zanie in "Open source security at Astral"

zanie — Thu, 09 Apr 2026 12:16:43 +0000

We do address this in the article! It's defense in depth, not theater.

We audit all of our actions, check if they pull in mutable dependencies, contribute upstream fixes, and migrate off using any action when we can.

(I work at Astral)

New comment by zanie in "Astral to Join OpenAI"

zanie — Thu, 19 Mar 2026 14:42:57 +0000

A brief note, your numbers are way off here — Astral subsequently raised a Series A and B (as mentioned in the blog post) but did not announce them. We were doing great financially.

(I work at Astral)

New comment by zanie in "Announcing the Beta release of ty"

zanie — Wed, 17 Dec 2025 19:10:33 +0000

Ruff wasn't named after the bird, we just think it's funny that Charlie didn't know it was a bird. He made up the word :)

New comment by zanie in "Announcing the Beta release of ty"

zanie — Tue, 16 Dec 2025 23:21:15 +0000

This is also documented at https://github.com/astral-sh/ty?tab=readme-ov-file#contribut... and https://github.com/astral-sh/ty/blob/main/CONTRIBUTING.md#re...

New comment by zanie in "Announcing the Beta release of ty"

zanie — Tue, 16 Dec 2025 22:21:19 +0000

As noted in the linked issue

> At time of writing, many of the remaining rules require type inference and/or multi-file analysis, and aren't ready to be implemented in Ruff.

ty is actually a big step in this direction as it provides multi-file analysis and type inference.

(I work at Astral)

New comment by zanie in "Uv is the best thing to happen to the Python ecosystem in a decade"

zanie — Thu, 30 Oct 2025 16:57:27 +0000

You're upset that uv doesn't yet support something that no other tool in the ecosystem supports?

I'd love for uv to lock build dependencies, but due to the dynamic nature of Python package metadata it's quite a hard problem. It'll be supported eventually though.

(I work on uv)

New comment by zanie in "Code formatting comes to uv experimentally"

zanie — Fri, 22 Aug 2025 17:44:17 +0000

It's intentionally distinct from the `uv tool` interface — it won't change `ruff` or `uv tool run` behaviors.