Closed pylint-bot closed 8 years ago
Original comment by Buck Evan (BitBucket: bukzor, GitHub: @bukzor?):
I'm getting this as well. This blocks us from using the current pylint.
Original comment by Buck Evan (BitBucket: bukzor, GitHub: @bukzor?):
I believe this change fixes this error, but it needs released on pypi:
https://bitbucket.org/logilab/astroid/commits/5ed6266cab789bc89d882444c938f03953491496
Original comment by Buck Evan (BitBucket: bukzor, GitHub: @bukzor?):
I've issued a pull request to add a regression test for this issue: https://bitbucket.org/logilab/pylint/pull-request/67/a-regression-test-for-namedtuple/diff
The test fails under current pyPI astroid (1.0.0), but passes under hg tip astroid (9cf54b49a2d4). I've opened an issue against astroid to get the necessary fix pushed to pyPI, which will finally close this issue, here: https://bitbucket.org/logilab/astroid/issue/6/please-update-pypi
Original comment by Sylvain Thénault (BitBucket: sthenault, GitHub: @sthenault?):
fixed by astroid 1.0.1
Originally reported by: Grzegorz Niewisiewicz (BitBucket: grn)
pylint crashes on code that uses attributes of a
namedtuple
.To reproduce do the following:
pylint
repository withhg clone https://bitbucket.org/logilab/pylint
cd pylint
andpython setup.py develop
test.py
PYTHONPATH=.. pylint test.py
.It produces the following output:
I expect it not to crash in this case.