Ruff v0.16.0 – Significant new updates – 413 default rules up from 59

Re:Ruff v0.16.0 – Significant new updates – 413 default rule... by 9dev on Sunday July 26, 2026 @08:44AM (#49057584)

I can - in fact, I have to, a lot more than I'd like - when someone makes changes with different code style settings in their IDE or tooling, and that affects unrelated parts of the code, and suddenly the PR contains tons of code that just looks subtly different but still does the same thing.

If sieving the spam from ham in code reviews is your thing, go have fun.

I personally prefer code that is automatically and unconditionally kept in the exact same shape, preserving only the intended changes to stop the team from wasting time on formatting or reviewing.

[ Parent | on HN ]

Re:Ruff v0.16.0 – Significant new updates – 413 default rule... by insanitybit on Sunday July 26, 2026 @08:48AM (#49057637)

That seems like a problem caused by an autoformatted, not solved by one. Obviously having reviewable commits is a reasonable expectation but that doesn't seem like a justification at all.

[ Parent | on HN ]

Re:Ruff v0.16.0 – Significant new updates – 413 default rule... by 9dev on Sunday July 26, 2026 @09:44AM (#49058185)

Pretty much all tools developers use to write code format code to some extent while editing, but often with individual configuration knobs or default settings that are different between all ICs.

Having a single tool that runs before committing, ideally as a git hook, ensures a single, uniform style across all files touched.

[ Parent | on HN ]