-
Notifications
You must be signed in to change notification settings - Fork 48
linting fails when .pylintrc is present #236
Comments
I have the same issue. I am using ubuntu 16.04 and install pylint in a virtual env. |
Check this highlighted section of Pylint code, as well as the diff starting where I highlighted down to line 650. You can also see these changes were added in Pylint 1.8.0 at the top of the diff. Do you see what's going on, and why, even when the commit was made half a year ago, it's just now affecting us? This all happened because of this issue. The linter-pylint error is happening because, as of 1.8.0, Pylint now sends |
can confirm that applying @gucciferXCIV 's fix in #237 and then manually building the extension using |
So how could I fix this issue? (I do not understand javascript) I tried adding the .+$ but it still doesn't work... Do I need to compile it somehow? I'm new to atom. Please help! |
Bump |
I am currently encountering this error. When reviewing the console it was clear when my pylintrc file was not properly specified but now I'm stumped! Below is the console output
|
I have a
.pylintrc
file that works just fine when I use the command line:In Atom (linter-pylint 2.1.0) things work fine if I do not have a .pylintrc file, but as long as I do, I get a dialog that pops up that says:
This is what it says in the console:
If I remove the .pylintrc file everything works fine.
linter-pylint finds my .pylintrc whether it's in the current directory or my home directory, but I get the same behavior in both cases.
This happens regardless of the .pylintrc contents. In my case I generated the .pylintrc file with the command:
...and did not modify it at all. I would like to, but only after this is resolved.
I'm working in a virtual environment (with pylint 1.8.1 installed in the virtualenv) and python 3.6.3, on macOS 10.12.6.
The text was updated successfully, but these errors were encountered: