Skip to content
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

augmentation: use ScopeConsumer instead an array #121

Merged
merged 1 commit into from
Jan 24, 2018

Conversation

simobasso
Copy link
Contributor

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

@antdking
Copy link

antdking commented Jan 23, 2018

pylint version will need setting to pylint>=1.8.2, as this is when ScopeConsumer and NamesConsumer are introduced

@simobasso
Copy link
Contributor Author

@cybojenix Thanks for review! Update ASAP

@simobasso
Copy link
Contributor Author

@cybojenix pinned!

@asherf
Copy link

asherf commented Jan 24, 2018

I am hitting this issue too. Thanks for fixing
https://travis-ci.org/hearsaycorp/django-richenum/jobs/332640253
screenshot 2018-01-23 21 53 42

@atodorov
Copy link
Contributor

I can reproduce locally with the existing test suite. Merging and will release a new version in a few minutes.

@atodorov atodorov merged commit b4fd85d into pylint-dev:master Jan 24, 2018
@simobasso simobasso deleted the fix_120 branch January 25, 2018 09:44
@simobasso
Copy link
Contributor Author

🎉 @atodorov thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TypeError: 'NamesConsumer' object does not support indexing
4 participants