Remove redundant migration blacklisting if possible #289
Labels
Comments
carlio
added a commit
that referenced
this issue
Aug 28, 2020
…the plugin is loaded, migrations are added to the blacklist. The migrations checker then removes them from the blacklist, and since it edits linter.config, it is not only done for the migrations checker but globally. Therefore the plugin should simply not manage the blacklist for migrations (also avoiding overriding any user-specified behaviour in their .pylintrc)
carlio
added a commit
that referenced
this issue
Aug 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Adding to the list of 'do not check these paths' for migrations is done in two places:
https://github.com/PyCQA/pylint-django/blob/master/pylint_django/checkers/migrations.py#L159
https://github.com/PyCQA/pylint-django/blob/master/pylint_django/plugin.py#L21
This should be removed unless there is some reason that it is repeated.
The text was updated successfully, but these errors were encountered: