-
Notifications
You must be signed in to change notification settings - Fork 117
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
TypeError: 'NamesConsumer' object does not support indexing #120
TypeError: 'NamesConsumer' object does not support indexing #120
Comments
pylint-dev/pylint@d343169 had introduced NamesConsumerAtomic (renamed in ScopeConsumer in pylint-dev/pylint@b80d76d). ref pylint-dev/pylint@d343169 ref codacy/codacy-pylint#29 fix pylint-dev#120
pylint-dev/pylint@d343169 had introduced NamesConsumerAtomic (renamed in ScopeConsumer in pylint-dev/pylint@b80d76d). ref pylint-dev/pylint@d343169 ref codacy/codacy-pylint#29 fix pylint-dev#120
pylint-dev/pylint@d343169 had introduced NamesConsumerAtomic (renamed in ScopeConsumer in pylint-dev/pylint@b80d76d). ref pylint-dev/pylint@d343169 ref codacy/codacy-pylint#29 fix #120
I'm getting this error with pylint=1.8.4 and pylint-django=0.8.0. I'm on Python 2, so updating to 0.9.0 or beyond is not a possibility yet. Can we get this fix backported to 0.8.0? |
^^ Ignore that, brain fade on my part |
@carlio I don't understand how prospector2 relates to pylint-django? |
@nedbat oh sorry. It does not at all. I had too many tabs open and got confused please ignore those comments! |
pylint-dev/pylint@d343169 had introduced NamesConsumerAtomic (renamed in ScopeConsumer in pylint-dev/pylint@b80d76d). ref pylint-dev/pylint@d343169 ref codacy/codacy-pylint#29 fix #120
@nedbat can you try the backport_120_to_0.8 branch ? I have cherry-picked the commit that originally fixed this but CI fails because we've dropped testing on Py2 and dependent components already require the latest versions of pylint/astroid. |
I cherry-picked the commit onto my own fork (https://github.com/nedbat/pylint-django/tree/nedbat/scopeconsumer) and ran with it, and I didn't get this error. I did have a separate problem that pylint suddenly stopped in the middle of a large run, though I'm not sure how I'm going to debug that... |
@nedbat, @carlio I'm not sure what course of action to take here:
|
Thanks, I appreciate the difficulty of maintaining an 0.8.x branch. At this point, we are not moving up to this code anyway until I have time to reproduce and diagnose why pylint stops completely. |
pylint-dev/pylint@d343169 had introduced NamesConsumerAtomic (renamed in ScopeConsumer in pylint-dev/pylint@b80d76d). ref pylint-dev/pylint@d343169 ref codacy/codacy-pylint#29 fix #120
how to reproduce:
freeze
R0201.py
command
output
expected (as pylint 1.7.5 works)
The text was updated successfully, but these errors were encountered: