Uv format: Code Formatting Comes to uv (experimentally)

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 formatter as a separate tool.

The analogy would be to Cargo: `cargo fmt` just runs `rustfmt`, but you can also run `rustfmt` separately if you want.

I think the goal is to make uv a complete package manager for Python while still giving you the option to use the parts separately.

uv is like cargo for python.

If you only need a fast type checker you can just use ty, if you just need a fast formatter and linter you can just use ruff.

Combining ruff and ty doesn't make sense if you think about like this.

They are mimicking Rust's cargo, which has `cargo fmt`

But what if `ty` was also eventually merged into `uv` as well? 8-)

That's probably the vision, given all from astral.sh, but `ty` isn't ready yet.

This is the direction I expected things to go, and not something I'm especially fond of. I'll stick with UNIX-philosophy tools, thanks.

It's really difficult to do Python projects in a sound, reproducible, reasonably portable way. uv sync is in general able to build you only a package set that it can promise to build again.

But it can't in general build torch-tensorrt or flash-attn because it has no way of knowing if Mercury was in retrograde when you ran pip. They are trying to thread a delicate an economically pivotal needle: the Python community prizes privatizing the profits and socializing the costs of "works on my box".

The cost of making the software deployable, secure, repeatable, reliable didn't go away! It just became someone else's problem at a later time in a different place with far fewer degrees of freedom.

Doing this in a way that satisfies serious operations people without alienating the "works on my box...sometimes" crowd is The Lord's Work.

Are they baked into the main executable or are they separate binaries (a la apt, cargo, etc)?

> Try out uv format in your next project and see how it fits into your development workflow. The experimental nature means your feedback could help shape how this feature evolves.

So maybe nobody has been waiting for this and the feedback will be: we don’t need this.

Also it uses ruff under the hood. If it’s integrated with uv, an advantage is one less tool to juggle.

I've been waiting.

uv is trying to deliver the same experience as cargo does for rust. Just install a single CLI and it's the only tool you have to worry about when working on your Python project.

There's nothing wrong with `ruff format`, but it's nice to have `uv` as a universal entrypoint.

Well, the same functionality used to be bundled into rye before the switch to uv. I appreciate having one less dependency to declare again.

ty is already in the same repo as ruff, so integrating seems likely

I think the biggest thing is that it doesn't seem to support other formatters. If my project uses black I don't get to have uv format work for me.

What is your first choice?

It really does sound like a bad idea, and now that I've used cargo a lot, I want a lot more of those bad ideas in my life.

Seriously, if uv becomes to Python what cargo is to Rust, the developer experience for Python is going to be vastly better than before. I've been writing Python professionally for more than 25 years, and getting paid to work around it's crummier parts, and I'm thrilled to be able to throw away all that knowledge and just use uv.

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

You realize this is just a shortcut for one of those "time-tested" options, right? ruff format is already widely used.

Because that's a way less obvious command.

that’s a bit slow typically

Also needs to make sorting imports a default.

FWIW, you can pretty easily script this sort of thing. In Bash it can even be a function added to your ~/.bashrc .