-
-
Notifications
You must be signed in to change notification settings - Fork 397
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 config #2583
base: master
Are you sure you want to change the base?
Add Ruff config #2583
Conversation
Those fix ruff warnings like: B904 Within an `except` clause, raise exceptions with `raise ... from err` or `raise ... from None` to distinguish them from errors in exception handling
Weird we didn't catch those before
@phw ruff could replace isort, pylint, and flake8 we have configs for, so that's a first step. I created a separated workflow for now, but we may want to actually replace pylint in existing workflows. Those related to raise ... from are trickier, most of times we want to use from parent exception, but in case we actually handle it, so I tried to stick to some ... logic. A review is very needed though ;) Question: should'nt we write a proper pyproject.toml with a project section now? |
Summary
Problem
Solution
Action
Additional actions required: