Open DeepSpace2 opened 5 years ago
This issue has been automatically marked as stale because it has not had activity in the last 60 days.
I think this is issue with ignore (and probably ignore-patterns) because I have the same problem but some other options that I am using seem to work
The same with Pitirus, "ignore" does not work. In command line, "ignore" works just fine.
Same problem here, when I click the 'check project' icon in the IDE the pyline.exe command is passed a full list of .py files to check. The --ignore=directory command line entry or the entry in the .pylintrc file are ignored.
Both these options work correctly when run pylint from the Terminal so I know the .pylintrc file and/or the --ignore option is working.
Seems that the plugin is sending everything, which we could say it shouldn't, and the pylint.exe is overriding the ignore options if the file has been explicitly passed on the command line.
If I mark a folder as Excluded in PyCharm the the directory is not passed to pylint but I'd rather the config/command line switches dealt with it rather than any IDE project setting.
Will this be fixed soon ? I seem to run this problem as well, although when I run pylint through command it seems to respect .pylintrc
This issue has been automatically marked as stale because it has not had activity in the last 60 days.
+1
This issue has been automatically marked as stale because it has not had activity in the last 60 days.
Just ran into the same problem. How about looking into this, instead of having the bot automatically mark it as stale after two months?
+1
FWIW, I figured out a way that seems to work for me:
In the settings of the plugin, there is an "Arguments" option. Use --rcfile /absolute/path/to/pylintrc
and now pylintrc
is respected.
I have the same problem. Command-line correctly ignores a given python file, but the plugin does not, ever though they are using the same .pylintrc
and executable.
This issue has been automatically marked as sadge because it has not had activity in the last 60 days.
FWIW, I figured out a way that seems to work for me:
In the settings of the plugin, there is an "Arguments" option. Use
--rcfile /absolute/path/to/pylintrc
and nowpylintrc
is respected.
Not the case for me, the behavior is the same.
+1
I found a solution that worked for my Windows PC.
I installed a Linux VM, where I configured PyCharm and Pylint. Then, I created a GitHub repository to upload .pylintrc file on the Linux VM. Finally, I downloaded on Windows the .pylintrc file from the repository and I specified the path to this file in the configuration of Pylint.
It worked, even after making changes to .pylintrc. The main bug I encountered was that sometimes (when running Pylint) it would use a previous version of .pylintrc, instead of the current one, but it can be fixed by restarting Pycharm.
Another year, another bump.
Step 1: Are you in the right place?
Step 2: Describe your environment
Step 3: Describe the problem:
Steps to reproduce:
Observed Results:
The scan executes as if no .pylintrc file was provided.
Expected Results:
The scan should respect the configuration from .pylintrc
Relevant Code:
project tree:
.pylintrc
file:Plugin settings:
Executing
pylint
from terminal,.pylintrc
is respected:However, when executing a scan from Pycharm both files are scanned.