←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: 0s | source
Show context
rcarmo ◴[21 Aug 25 20:58 UTC] No.44978004[source]▶
This feels like feature creep. I've been using uv more and more over the past year (mostly because I work with projects that use it) and although I like it and recognize the advantages, it is still not my first choice, and this kind of thing isn't going to help that...
replies(3): >>44978366 #>>44978369 #>>44980655 #
asa400 ◴[22 Aug 25 03:09 UTC] No.44980655[source]▶
What's wrong with this approach specifically? Go does it this way. Rust does it this way. Elixir does it this way. It reduces the toil in setting up and using projects in those ecosystems substantially. It unifies community effort behind a common set of tools and provides beginners and experts alike with a shared entrypoint to projects.
replies(2): >>44980918 #>>44980925 #
1. fluidcruft ◴[22 Aug 25 04:12 UTC] No.44980925[source]▶
One thing I wonder about is what happens in pyproject? Do you use tool.ruff/tool.ruff.format or tool.uv.format or what? Are people who only know "uv format" supposed to understand that part? Does ruff start honoring tool.uv.format? Which have priority over which in search. Does it behave differently when you run uv format vs ruff format? etc