-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
nix: setup linter to lint python files (pt II) #4377
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
base: main
Are you sure you want to change the base?
Conversation
No need for the
Why ignore Overall, this looks nice, but this looks like a lot of change and it is a bit harder to judge and review. @jenstroeger How about only clearing one warning |
Ruff claims to replace Black as well, if you want to risk that…
Fairnuff.
You should be able to cherry-pick commit 7ceb260 for that, no? Or should I open a separate PR for that you can merge? |
Yes please do with just one commit/change, so we can review easily. Also, we follow commit message conventions, |
Draft PR #4382
Agreed, I’m a fan of conventional commits myself 👍🏼 |
@taimoorzaeem the PR we discussed here.
A few additions:
Turns out there was much noise for a few fairly straightforward changes, and now the code is cleaner:
Out of curiosity I also ran perflint:
which came back with a few suggestions. Happy to add some of those (perhaps not all) if an iota of performance increase matters 🤓
Also, I did not actually run these changes… 😇