-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Incorrect 'unsubscriptable-object' reported #3139
Comments
Downgrading to pylint<2.4 and astroid<2.3 appears to resolve this. Notably, downgrading only pylint does not help. x-ref: https://gitlab.tiker.net/inducer/pytential/merge_requests/182 |
Thank you for reporting the issue, I can reproduce it as well. |
@atilag, the PR pylint-dev/astroid#732 should fix this issue. |
I am using pylint 2.4.4. It still shows the error. |
This should be fixed with the release of |
Astroid 2.4.1 and pylint 2.5.2 My error raise from pymongo db e.g |
… pylint updated because the bug pylint-dev/pylint#3139
I can reproduce the original issue as well. I don't believe this issue has been fixed or it momentarily was and the issue resurfaced with newer versions. pylint 2.6.0 |
@acxz thanks for your report. However i can not reproduce the original issue. For example linting the following code:
gives:
with:
|
Thanks for looking into this, @hippo91! I cannot reproduce the issue with the original script either.
gives:
with
Should I instead make a new issue for this snippet? We can just track this over at #3637 |
Steps to reproduce
Running pylint 2.4.1 to this code will want about incorrect 'unsubscriptable-object':
Current behavior
Running pylint warns:
Expected behavior
No warn
pylint --version output
pylint 2.4.1
astroid 2.3.0
Python 3.7.2 (default, Dec 29 2018, 00:00:04)
[Clang 4.0.1 (tags/RELEASE_401/final)]
Maybe related to: #3129 ?
The text was updated successfully, but these errors were encountered: