-
Notifications
You must be signed in to change notification settings - Fork 438
pyflakes (pylint, ruff, ....) clean-up, CI? #1101
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
Comments
See python-control/Slycot#246 for applying See here for CI test result failing with |
Yes!
Not on my end.. I've tried running |
Yes, let's do this! In the past I used |
after struggling with pyflakes, I'm try ruff with "pyflakes-only" warnings, and add some "# noqa" lines to |
Addressed in #1118. OK to close, unless there is additional discussion of what we want to do. |
Running pyflakes on main HEAD (0ff0452) reveals lots of possible issues; see end.
Is there interest in getting and keeping the tree lint-clean?
This would require some changes to style, e.g., dropping
from foo import *
(see output below), and some patience when the linter spits out an incomprehensible message.Are there strong preferences for a particular linter?
I use pyflakes often: it's simple, has a low false-positive rate, but is not configurable.
The other two I'm aware of:
pyflakes output:
The text was updated successfully, but these errors were encountered: