Support pylint --load-plugins option in profile

[SergeyKosarchuk]

Hi!
Is --load-plugins tool option for pylint supported by profile configuration file? Seems like this option has no effect. Here is my .prospector.yaml file.

pylint:
  disable:
    - unused-argument
    - too-few-public-methods
    - too-many-arguments
    - too-many-ancestors
    - redefined-outer-name
    - relative-beyond-top-level
  load-plugins:
    - custom-plugin

I am using prospector==1.1.6.2 and pylint==2.1.1.

[Kilo59]

I recently discovered this as well and may have to stop using Prospector on a few projects because of it.

I'd be happy to try to add this if someone could point me in the right direction.

I noticed that Prospector does seem able to use a select few pylint plugins.
https://prospector.readthedocs.io/en/master/profiles.html#libraries-used-and-autodetect

But using uses: - custom-plugin does not appear to work either

[chocoelho]

Hey there @Kilo59 @SergeyKosarchuk, as of now options are limited to pylint-django, pylint-celery and pylint-flask. Sure, we can work something out to make it more flexible, but @carlio and I are kinda short-handed here. We always welcome new PRs to integrate new features, and some points worth checking are:

• https://github.com/PyCQA/prospector/blob/master/prospector/tools/pylint/__init__.py#L29
• https://github.com/PyCQA/prospector/blob/master/prospector/tools/pylint/linter.py#L20

Also, you could always use pylint own .pylintrc while this is not yet implemented :) LMK if that works

[SergeyKosarchuk]

Hey @chocoelho, thank you for help. Seems like a good opportunity for PR.

[chocoelho]

Closing this as prospector 1.1.7 should implement this issue.