Ruff: Python linter and code formatter written in Rust

Re:Ruff: Python linter and code formatter written in Rust by ubercore on Tuesday January 21, 2025 @02:51AM (#42777545)

Working on a team in a larger python application, type checkers and linters are such a time saver. It's so nice not to think about how I'd like to format my code any longer. We've made some tweaks to our ruff rules to suit the team's opinion, and now even when I don't _love_ the way it formats a particular part of code, I just move on and get something productive done instead.

And type checking is so great for both preventing bugs (which it does all the time) and self-documenting code. Can't recommend them enough.

[ Parent | on HN ]

Re:Ruff: Python linter and code formatter written in Rust by Dries007 on Tuesday January 21, 2025 @03:49AM (#42777837)

It takes out so much frustration too. No more nitpicking about style/... in merge requests, the pre-commit hook will fix it and CI will catch it if you don't.

The more of this you can automate, the more you get to spend on "real work".

[ Parent | on HN ]

Re:Ruff: Python linter and code formatter written in Rust by E_Bfx on Tuesday January 21, 2025 @03:12AM (#42777641)

In my organisation, some co-workers used to write def func(*args,**kwargs) all the time. That was so tiring to look for what you should put as argument. Type checking is mandatory for well organized large project.*

[ Parent | on HN ]

Re:Ruff: Python linter and code formatter written in Rust by scosman on Tuesday January 21, 2025 @07:27AM (#42779369)

Yes yes yes.

I have my own formatting preferences, but my desire to not have to think about them or go to meetings debating them is much much greater.

[ Parent | on HN ]