-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
chore: fixing pylint
issues
#8610
Conversation
Pull Request Test Coverage Report for Build 12240140835Details
💛 - Coveralls |
adding @anakin87 as well |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking care of this.
Looks good in general, but I left some suggestions.
In the long term, I would prefer to keep the current (default) value of max-positional-arguments
, so that when adding new code, we are aware of this and behave correctly.
I actually agree on this, maybe we can do it on another PR? WDYT @anakin87? Edit: saw that you don't want to do it. Other changes LGTM! |
@mpangrazzi we can do discuss how to do it or do it in another PR. For now I just wanted to fix this so that I pylint doesn't raise any issues when running it locally. |
@anakin87 trying to the fix the |
|
@davidsbatista I pushed a commit (c389a57) to show what I mean: once you modify the method, you should also modify the caller and related tests. |
ok, I see, thanks 👍🏽 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙏
Proposed Changes:
I'm fixing the issue with
pylint
, which locally runs over all files. Since the last update (I suppose topylint
), it makes the local linting process raise an issue for functions with more than 5 positional arguments, which we have a lot of.We should probably increase this number to slightly more than 5 in
pyproject.toml
, e.g.:max-positional-arguments = 10
and then iteratively remove this disablement as we refactor some of the functions.How did you test it?
I successfully ran pylint on
main
branch in my local environment without pylint raising any issues.Checklist
fix:
,feat:
,build:
,chore:
,ci:
,docs:
,style:
,refactor:
,perf:
,test:
and added!
in case the PR includes breaking changes.