-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
False positive error report E1101 with EnvironmentError #2777
Closed
plocharz-9livesdata opened this issue
Feb 28, 2019
· 2 comments
· Fixed by jacoblearned/pycodeflow#4, python-trio/trio#963, ChrisRBe/PP-P2P-Parser#88, toastwaffle/LiME#69 or thermondo/stanley#224
Closed
False positive error report E1101 with EnvironmentError #2777
plocharz-9livesdata opened this issue
Feb 28, 2019
· 2 comments
· Fixed by jacoblearned/pycodeflow#4, python-trio/trio#963, ChrisRBe/PP-P2P-Parser#88, toastwaffle/LiME#69 or thermondo/stanley#224
Comments
Yikes, thanks for reporting the issue! What's happening is that the inference engine is dumb and can't limit the inference of |
This is fixed in astroid's master which is going to be astroid 2.3.0 when launched. |
This was referenced Mar 4, 2019
PCManticore
added a commit
to pylint-dev/astroid
that referenced
this issue
Mar 8, 2019
This was referenced Mar 8, 2019
This was referenced Apr 1, 2019
This was referenced Apr 10, 2019
This was referenced May 27, 2019
This was referenced Jun 7, 2019
This was referenced Jun 24, 2019
This was referenced Aug 28, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
test-pylint.py
Steps to reproduce
pylint -E test-pylint.py
Current behavior
Expected behavior
No output is expected
Workaround:
Use different names for error variables:
pylint --version output
The text was updated successfully, but these errors were encountered: