pylint-bot
commented
8 years ago Original comment by BitBucket: afahim, GitHub: @afahim?:
I can confirm the above. Had to pin astroid version to 1.3.8 to get pylint 1.4.4 to keep working. Works for now, would be nice if the issue gets resolved however.
Here is a stacktrace.
#!python
Traceback (most recent call last):
File "/home/travis/virtualenv/python2.7.9/bin/pylint", line 11, in <module>
sys.exit(run_pylint())
File "/home/travis/virtualenv/python2.7.9/lib/python2.7/site-packages/pylint/__init__.py", line 20, in run_pylint
from pylint.lint import Run
File "/home/travis/virtualenv/python2.7.9/lib/python2.7/site-packages/pylint/lint.py", line 30, in <module>
from pylint.checkers import utils
File "/home/travis/virtualenv/python2.7.9/lib/python2.7/site-packages/pylint/checkers/__init__.py", line 46, in <module>
from astroid.utils import ASTWalker
ImportError: No module named utils
Originally reported by: Paul Michali (BitBucket: paul_michali)
In openstack.org's neutron project, using pylint 1.4.4, when astroid updated to 1.4.1 pylint failed with many non-sensical errors. For example, use of any module from an import was showing a undefined variable error in pylint, which worked fine with astroid 1.3.8 and pylint 1.4.4. We see the same issue with astroid 1.4.0 as well.
E.g.
import abc import six ... @six.add_metaclass(abc.ABCMeta)
Plyint would report undefined variable for 'abc' and 'six'. This happens for every import in every file.