←back to thread

Code formatting comes to uv experimentally

(pydevtools.com)
365 points tanelpoder | 2 comments | 21 Aug 25 20:26 UTC | HN request time: 0s | source
Show context
thanhhaimai ◴[21 Aug 25 21:20 UTC] No.44978239[source]▶
I'd rather `ruff` being merged with `ty` instead. `uv` for me is about package / project manager. It's not about code style. The only time `uv` should edit a code file is to update its dependencies (PEP 723).

On the other hand, both `ruff` and `ty` are about code style. They both edit the code, either to format or fix typing / lint issues. They are good candidates to be merged.

replies(7): >>44978308 #>>44978351 #>>44978465 #>>44978499 #>>44978500 #>>44979712 #>>44981364 #
WD-42 ◴[21 Aug 25 21:28 UTC] No.44978308[source]▶
They are mimicking Rust's cargo, which has `cargo fmt`
replies(3): >>44978332 #>>44981211 #>>44984775 #
1. petcat ◴[22 Aug 25 13:58 UTC] No.44984775[source]▶
Doesn't cargo just have a subcommand plugin system? Or is fmt actually hard-coded into the cargo code?

I prefer the plugin system. I don't like god programs like what the npm monstrosity became.

replies(1): >>44985227 #
2. woodruffw ◴[22 Aug 25 14:38 UTC] No.44985227[source]▶
cargo has an external subcommand system, but it also has "blessed" (my word choice) external subcommands that are typically bootstrapped via Rust toolchain components. This makes them pretty analogous to what uv does here with `uv format`, in my opinion.