-
-
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
module 'pylint.checkers.utils' has no attribute 'is_call_of_name' // pylint 2.6.1 #4096
Comments
experiencing the same issue with pylint==2.6.1 |
Thank you for the report, we're having some trouble following the release of astroid
Edit : pylint |
Also bitten by the regression. |
Details: * The latest release 2.6.1 of Pylint has an issue resulting in AttributeError: module 'pylint.checkers.utils' has no attribute 'is_call_of_name' See pylint-dev/pylint#4096. To circumvent that, this change excluded pylint 2.6.1 and astroid 2.5.0 for now. Signed-off-by: Andreas Maier <maiera@de.ibm.com>
Details: * The latest release 2.6.1 of Pylint has an issue resulting in AttributeError: module 'pylint.checkers.utils' has no attribute 'is_call_of_name' See pylint-dev/pylint#4096. To circumvent that, this change excluded pylint 2.6.1. The proposal made in the pylint issue to also exclude astroid 2.5.0 is not necessary (at least not for our use cases). Signed-off-by: Andreas Maier <maiera@de.ibm.com>
I was trying to verify that excluding pylint 2.6.1 alone is sufficient (see PR posts above), but it turns out pylint 2.6.2 had just been released some minutes ago and it succeeds again. Thanks much for the very quick turnaround!! |
No problem, I don't like seeing issues with a new thumbs up every 3 minutes :D Made me realize that pinning pylint is the way to go as a new version can make a build fail because of new messages anyway. |
Hi All,
after the update to 2.6.1 version I'm getting the following error in every .py file:
AttributeError: module 'pylint.checkers.utils' has no attribute 'is_call_of_name'
has anyone already experienced this?
Best,
Alexey
The text was updated successfully, but these errors were encountered: