-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
False positive no-value-for-parameter
in Pylint 2.5
#3563
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
Labels
Comments
PCManticore
added a commit
that referenced
this issue
May 2, 2020
PCManticore
added a commit
that referenced
this issue
May 2, 2020
Wow that was quick. Thanks! |
Sorry for waking this up, but I'm having the same error with pylint 2.6.2, astroid 2.4.2. Is this known or do I have to open a new bug? |
ibaoger
pushed a commit
to ibaoger/pdfium
that referenced
this issue
Nov 24, 2021
This CL includes: * set Pylint version to 2.7 * pass skip_shebang_check=True to RunUnitTestsInDirectory And fixes some Pylint warnings: * W0406: fix import-self * E1101: Set name and aliases as an abstract property in encode_pdf_filter.py since name and aliases are introduced in subclasses. * E0012: Remove Py2 hint of # pylint: disable=relative-import * R0205: Replace all "class ClassName(objects)" with "class ClassName" * E1120: Ignore this error. see pylint-dev/pylint#3563 * W0707: explicitly re-raising using the 'from' keyword Bug: pdfium:1674, chromium:1262354, chromium:1262297 Change-Id: I205d254514f1ae667af818c789b5e6d89a061c68 Reviewed-on: https://pdfium-review.googlesource.com/c/pdfium/+/87270 Reviewed-by: Lei Zhang <[email protected]> Commit-Queue: Lei Zhang <[email protected]>
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
In
bug.py
:Run
pylint bug.py
(no user config necessary).Current behavior
In
Pylint==2.5.0
(see below for detailed versions):With
Pylint<2.5
:Expected behavior
good
andbad
are effectively the same thing, and both are bug-free. I would expect no errors from Pylint.Also, I don't get why the argument name is inferred as
a
?pylint --version output
For
Pylint==2.5.0
(first case above):For
Pylint<2.5
:The text was updated successfully, but these errors were encountered: