Allow pylint installation outside of project environment
chr1st1ank opened this issue · comments
Is your feature request related to a problem? Please describe.
I installed pylint on system level and it even is on the PATH. But also when I specify the absolute path of the system wide installation (/usr/bin/pylint) the plugin doesn't find it. This is related to #47 where the outcome seems to be that it must be installed in the respective project environment.
Describe the solution you'd like
Accept an absolute path to a system wide pylint installation.
Describe alternatives you've considered
The plugin forces me to install pylint in each and every project interpreter (wether it being a venv, pipenv, conda environment etc). If I don't because I don't need Pylint for a particular project, I'll get a popup warning that the pylint executable couldn't be found.
Adding tools like pylint, mypy, pytest etc. to the pipenv has side effects: They are also installed by any CI/CD pipeline setting up the project environment. This slows down the whole process. Also if these packages are not filtered out manually, they will get installed in production in the deployment step (depending on what type of environment is used and if it provides a "dev" mode).
Additional context
Versions used:
- PyCharm Community 2019.2.3
- Pylint plugin 0.11.1
This issue has been automatically marked as stale because it has not had activity in the last 60 days.