←back to thread

Code formatting comes to uv experimentally

(pydevtools.com)
365 points tanelpoder | 1 comments | 21 Aug 25 20:26 UTC | HN request time: 0.208s | 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 #
zahlman ◴[21 Aug 25 21:45 UTC] No.44978465[source]▶
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.
replies(5): >>44978583 #>>44979916 #>>44979956 #>>44980082 #>>44981479 #
zem ◴[21 Aug 25 21:57 UTC] No.44978583[source]▶
this is very much in line with the unix philosophy - it delegates formatting to ruff and simply provides a unified front end that calls out to the right specialized tool. think of it as a makefile.
replies(3): >>44978776 #>>44982952 #>>44983430 #
1. zvr ◴[22 Aug 25 10:52 UTC] No.44982952[source]▶
A better example might be: in good ol' days when we were formatting with troff(1), passing arguments to the command line invoked other programs like eqn(1) and tbl(1).