Viewing profile — zanie

We want to support that workflow / experience but we want to design it differently because there are a lot of nuances to pip's interface and the pip maintainers have encouraged us …

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 …

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

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…

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…

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 …

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 creati…

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 th…

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.

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 ima…

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.

(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/settin…

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…

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 s…

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 migra…

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…

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 :)

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...

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 …

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…

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

Thanks that's helpful. Did you try reducing the concurrency limit?

Please open an issue with some details about the memory usage. We're happy to investigate and feedback on how it's working in production is always helpful. (I work on uv)

Thanks for the feedback!

Yes, we let you override our detection of your hardware. Though we haven't implemented dumping detected information on one platform for use on another, it's definitely feasible, e.…