News for hackers. Stuff that matters.
Re:Uv format: Code Formatting Comes to uv (experimentally) by d0mine on Friday August 22, 2025 @12:07AM (#44980903)
One can find repos using `make format` / `make lint`/ `make typecheck` / or similar

I remember David Beazley mentioning that code with Makefiles were relatively easier to analyze based on ~Terabyte of C++ code and no internet connection (pycon 2014) https://youtube.com/watch?v=RZ4Sn-Y7AP8

Re:Uv format: Code Formatting Comes to uv (experimentally) by Kwpolska on Friday August 22, 2025 @01:36AM (#44981326)
That `make format` command was not defined by the Make developers, but by the team using Make in their project. They picked their favorite formatter and defined a shortcut. In this case, the uv developers are forcing the command on everyone, and they're using it to cross-promote their own formatting tool.
Re:Uv format: Code Formatting Comes to uv (experimentally) by Hendrikto on Friday August 22, 2025 @06:04AM (#44982690)
They are not forcing anything on anyone. You can decide to never run `uv format` and ruff won’t even be installed.

You can use uv without ruff. You can use ruff without uv. You can invoke ruff yourself if that’s what you want. Or use any other formatter.

I don’t think I understand what your complaint is.

Re:Uv format: Code Formatting Comes to uv (experimentally) by asa400 on Friday August 22, 2025 @10:17AM (#44984997)
Other people having an opinion and creating their own software project to implement it is not “forcing” anyone to do anything.

The inverse would be no one is allowed to create any projects that you don’t personally agree with.

Re:Uv format: Code Formatting Comes to uv (experimentally) by wiseowise on Friday August 22, 2025 @12:51PM (#44986779)
Nobody is forcing you to use anything. Feel free to ignore it and use whatever flavor you like.