-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ruff as a linter in pre-commit #106
Comments
First, let's talk about A linter, in the context of programming, is a tool that analyzes source code to flag programming errors, bugs, stylistic errors, and suspicious constructs. The term originates from a Unix utility that examined C language source code. In Python, linters are used to enforce a consistent coding style and to catch certain types of errors before the code is even run. Using a linter can help to identify syntax errors, structural problems, code smells, and even more complex issues such as detecting unused variables or imports. The most modern Linter in context of Python is
|
Great idea, what config is needed so it plays nicely with |
From a quick look it seems like it should just work: Ruff and Black: https://beta.ruff.rs/docs/faq/#is-ruff-compatible-with-black |
You could also entirely replace black with ruff. We've done that multiple times and, subjectively, results stayed the same |
Isn't black basically doing the job of an opinionated linter already for us? But in a style thats encouraged by the psf? |
I'm not sure that ruff can not be configured to mimic black-formatter behaviour - so you'd keep the style encouraged by the psf! On top of that, I think the main advantages are, that it comes with so much more than just formatting (black and isort). Configured correctly, it can, among much more, inform you on upgrade-compitability - one of my personal favourites. |
As of version 0.1.2 |
I noticed there is no linter. ruff is a great option to use.
The text was updated successfully, but these errors were encountered: