Viewing profile — charliermarsh

These are the Python distributions we use in uv ( https://github.com/astral-sh/uv ), i.e., when you install Python with uv, you're installing from python-build-standalone. (Same go…

> Man, it's easy to be fast when you're wrong. But of course it is fast because Rust not because it just skips the hard parts of dependency constraint solving and hopes people don'…

I'm not super familiar with Bundler's architecture but I think the most impactful thing would be adopting uv's cache design, which is a big part of what makes uv so fast and should…

If there's anything else accompanying the error, do you mind filing an issue? I've been using the ty extension with Cursor for weeks and am having trouble reproducing right now.

We actually do want ty to be a first-class LSP (i.e., a complete alternative to Pylance and others), and it already supports nearly all of the features you'd expect. I use it as my…

The PEP includes the ability to enable (or disable) lazy imports globally via a command-line flag or environment variable, in addition to the import syntax.

Lazy imports have been proposed before, and were rejected most recently back in 2022: https://discuss.python.org/t/pep-690-lazy-imports-again/1966... . If I recall correctly, lazy …

All of our tools can be used independently and in coexistence with other tools. You can use `uv` with other build backends; you can use `virtualenv` to create your virtual environm…

We already develop a formatter: Ruff ( https://github.com/astral-sh/ruff ). Ruff and uv are built by the same team. `uv format` is just an optional front-end to `ruff format`.

`uv format` is just a front-end for `ruff format`. It isn't introducing a new formatter to the ecosystem or anything like that.

Yeah, you can definitely use `uvx ruff` (an alias for `uv tool run ruff`) to invoke Ruff. That's what I've done in my own projects historically. The goal here is to see if users li…

It's a separate binary -- we install Ruff if you invoke `uv format`. So if you don't invoke `uv format`, there's no impact on the binary size, etc.

Good questions. I don't think we'd ever deprecate Ruff because `uv format` exists, and adding `uv format` won't have any impact on Ruff's release cycles or development. The analogy…

To clarify, `ruff` and `uv` aren't being merged. They remain separate tools. This is more about providing a simpler experience for users that don't want to think about their format…

> Will `uv` inspect my local GPU spec and decide what the best set of packages would be to pull from Pyx? We actually support this basic idea today, even without pyx. You can run (…

uv works just as well with whatever Python you want to bring -- you're not required to use the Pythons that uv is capable of installing on your machine.

The piece of this apology that I have trouble understanding is this: > We thought the license in the root repo wasn’t that important, so we just generated one that we thought was o…

We didn't support those workflows until today. If you'd prefer a true diff: uv adds support for projects, cross-platform lockfiles, scripts, and Python installs

Thanks dang, I appreciate it. I'd suggest something like: uv: A unified alternative to Poetry, pipx, pyenv, and more

I wrote about it a bit here: https://github.com/astral-sh/rye/discussions/1342

Was this section removed? I'm not seeing it in the linked post.

Yeah, that's definitely within scope for what we're trying to build, and we've been hard at work on extending uv to support those workflows (platform-agnostic resolution, lockfiles…

(Thank you for this, it was really inspiring for me to read.)