4 ms·

> an experimental new command that Python developers have been waiting for: uv format Have developers really been waiting for this? What's wrong with ruff form

• loloquwowndueo 1y ago
  > 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.
  • _ea1k 1y ago
    I've been playing around with go quite a bit lately, and now think that being bundled is actually a really serious advantage. Being able to just to "go fmt", without needing any additional tools, is a really great thing about the language. The only danger that I can see (and it is a big one) is that Python doesn't have the same kind of consistency that go does. It might end up failing just because so many people use Python in such different ways.
    • worldsayshi 1y ago
      Yes, one advantage is that tools/editors will start to standardize on it. I quite enjoyed the seamless experience of go formatting as I started learning go. It felt like one less thing to worry about. Just worked.
• mintplant 1y ago
  Well, the same functionality used to be bundled into rye before the switch to uv. I appreciate having one less dependency to declare again.
• chippiewill 1y ago
  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.