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

Add urlpatterns to good_names instead of modifying const_rgx for com… #109

Closed
wants to merge 1 commit into from

Conversation

vinaypai
Copy link
Contributor

@vinaypai vinaypai commented Dec 27, 2017

Add common names to good_names instead of modifying const_rgx for compatiblity with pylint 1.8+

Fixes #108

atodorov pushed a commit to MrSenko/django-pylint that referenced this pull request Jan 17, 2018
atodorov pushed a commit to MrSenko/django-pylint that referenced this pull request Jan 17, 2018
atodorov pushed a commit to MrSenko/django-pylint that referenced this pull request Jan 18, 2018
atodorov pushed a commit to MrSenko/django-pylint that referenced this pull request Jan 18, 2018
atodorov pushed a commit to MrSenko/django-pylint that referenced this pull request Jan 18, 2018
atodorov pushed a commit that referenced this pull request Jan 18, 2018
for compatiblity with pylint 1.8+

Fixes #108
Original PR: #109
Obsolete PR: #111
@atodorov
Copy link
Contributor

Merged manually as part of #113, thanks.

@horejsek
Copy link

Looks like after this change is impossible to add custom good names to the own configuration. Following snippet is always reporting urlpatterns and so and when I remove own good names, then logger is reported instead. Before it was working together fine (version 0.7.2).

[MASTER]
load-plugins=pylint_django

[BASIC]
good-names=_,dt,e,f,default_app_config,logger

@horejsek horejsek mentioned this pull request Jul 17, 2018
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.

3 participants