[refs #289] Removed the management of blacklist for migrations. When …

…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)

pylint_django/checkers/migrations.py

@@ -156,20 +156,10 @@ def func(apps, schema_editor):
     return is_migrations_module(node.parent)
 
 
-def load_configuration(linter):  # TODO this is redundant and can be  removed
-    # don't blacklist migrations for this checker
-    new_black_list = list(linter.config.black_list)
-    if 'migrations' in new_black_list:
-        new_black_list.remove('migrations')
-    linter.config.black_list = new_black_list
-
-
 def register(linter):
     """Required method to auto register this checker."""
     linter.register_checker(NewDbFieldWithDefaultChecker(linter))
     linter.register_checker(MissingBackwardsMigrationChecker(linter))
-    if not compat.LOAD_CONFIGURATION_SUPPORTED:
-        load_configuration(linter)
 
     # apply augmentations for migration checkers
     # Unused arguments for migrations

pylint_django/plugin.py

@@ -18,9 +18,6 @@ def load_configuration(linter):
     name_checker.config.good_names += ('qs', 'urlpatterns', 'register', 'app_name',
                                        'handler400', 'handler403', 'handler404', 'handler500')
 
-    # we don't care about South migrations
-    linter.config.black_list += ('migrations', 'south_migrations')
-
 
 def register(linter):
     """