-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Enable no-value-for-parameters (pylint) #9633
Conversation
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
Pull Request Test Coverage Report for Build 4240927292
💛 - Coveralls |
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.
I might actually be tempted to put line-level suppressions on each of these in order to remove the option from .pylintrc
(which I definitely agree we should do), because these lines look like a pylint bug to me. __new__
is a special-cased staticmethod
, not a classmethod
like Pylint is suggesting it is, and it should be valid to use self
or super()
to access it.
I actually went over to Pylint to file this, to discover that Ikko had already done so: pylint-dev/pylint#8325. |
@jakelishman Yes, I am sorry for the delay. After making this PR, I was thinking about the specs and started to suspect a bug, sorry to have to go through this twice. Sorry to make you take the time to look into it. |
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.
Thank you for taking a look! +1 on line-level suppressions with # pylint: disable=no-value-for-parameter
so that we can enable the check globally
No need to apologise! I'm totally on board with wanting this check back, and it's fun that we've found another pylint bug from Terra. |
Close since it's not a priority. |
Summary
Related to #9614
Details and comments