-
Notifications
You must be signed in to change notification settings - Fork 208
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
Reduce/remove files from the exclusion list of pre-commit, prospector, yapf, pylint #2207
Labels
good first issue
Issues that should be relatively easy to fix also for beginning contributors
priority/quality-of-life
would simplify development
Comments
Quick statistics out of my current branch (columns: line number, filename, number of messages);
About 2/3 have <10 messages |
Once all files are processed, we should then check if there are leftover 'disable' that are actually not needed |
Actually, this can be a good first issue for anyone willing to help improve code quality - simply
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Issues that should be relatively easy to fix also for beginning contributors
priority/quality-of-life
would simplify development
We now still have a quite long blacklist of files not to be checked by pre-commit hooks (yapf, prospector).
Most of them only have 1/2 things to fix.
A simple script to check how many errors there are is the following (run it in a py3 venv with prospector installed):
(of course it can be changed to also show the specific errors etc.)
The idea is that we can already remove and fix most of those with few problems.
As once put in there they will always be checked and must be ok, it's better to first try to remove as many as possible of those that are simple to fix, and leave the complicated ones at the end.
The text was updated successfully, but these errors were encountered: