Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error message "Linter pylint is not installed" persists after "Disable this linter" is clicked #16796

Closed
alex75it opened this issue Dec 7, 2016 · 12 comments

Comments

Projects
None yet
@alex75it
Copy link

commented Dec 7, 2016

  • VSCode Version: Code 1.7.2 (7ba55c5, 2016-11-21T22:06:37.428Z)
  • OS Version: Windows_NT ia32 6.1.7601
  • Extensions:
Extension Author Version
python donjayamanne 0.5.5
csharp ms-vscode 1.5.3

Steps to Reproduce:

  1. Open a .py file.
  2. Open another .py file, add something and save.
  3. Error "Linter pylint is not installed" appears.
  4. Click on "Disable this Linter"
  5. Edit the file again and save.
  6. Error "Linter pylint is not installed" appears AGAIN.

Note.
Close and restart VS Code does not solve the issue.
I don't want pylint (it is too noisy).

Thanks,
Alessandro

@alex75it alex75it changed the title Error message "Linter pylint is not installed" persist after "Disable this linter" Error message "Linter pylint is not installed" persists after "Disable this linter" is clicked Dec 7, 2016

@pythonoma

This comment has been minimized.

Copy link

commented Dec 8, 2016

same for me on ubuntu 16.04

@MahonyCZ13

This comment has been minimized.

Copy link

commented Dec 8, 2016

Same for me on Win 10 build 14393.447

@bighomeyg

This comment has been minimized.

Copy link

commented Dec 23, 2016

Same for me on OSX 10.12 with VS Code 1.8.1

@sid8128

This comment has been minimized.

Copy link

commented Dec 27, 2016

This annoying pop-up can easily be turned off. Just add the following line to workspace setting file:
"python.linting.lintOnSave": false

@NableLucas

This comment has been minimized.

Copy link

commented Feb 8, 2017

Hi,
Set the configuration manually. Open or create file settings.json and set parameters.

Example for pep8

vscode/settings.json
{
"python.linting.pep8Enabled": true,
"python.linting.pep8Path": "C:/Python27/Scripts/pep8.exe"
}

for the pylint it`s same

{
"python.linting.pep8Path": "C:/Python27/Scripts/pylint.exe"
}

@kieferrm

This comment has been minimized.

Copy link
Contributor

commented Feb 22, 2017

This is an issue with the Python extension. Moved to https://github.com/DonJayamanne/pythonVSCode/issues/763. Please subscribe there.

@l00c00l

This comment has been minimized.

Copy link

commented Mar 25, 2017

I got this message too, even after I have installed it.

@minorpoet

This comment has been minimized.

Copy link

commented May 5, 2017

i am wondering how this plugin find python2 / 3 related packages installed via pip / pip3

@ManPython

This comment has been minimized.

Copy link

commented May 9, 2017

@NableLucas

for the pylint it`s same

Not exactly..

"python.linting.pep8Path": "C:/Python27/Scripts/pylint.exe"

Should be
"python.linting.pylintPath": "C:/Python27/Scripts/pylint.exe",

I think that problem is often if ppls has other path of Python in someProject.vscode\launch.json and the Pylint is instaled to other enviorment eg venv or Python27 or python34 or disc e:/

But I can confirm that I'm not happy from this all, and often have some strange issues around Pylint in VSC,

@boydthomson

This comment has been minimized.

Copy link

commented Jun 9, 2017

resolved this issue on VS Code for linux by changing:
"python.linting.pylintPath": "pylint"
to
"python.linting.pylintPath": "pylint3"

@uint16

This comment has been minimized.

Copy link

commented Jun 18, 2017

On Linux(Ubuntu 16.04) one of the following should work

Install pylint using apt
sudo apt install pylint

or change
"python.linting.pylintPath": "pylint"
to
"python.linting.pylintPath": "{your pylint package path}"

@existme

This comment has been minimized.

Copy link

commented Jul 4, 2017

This is an environment issue, just add the ~/.local/bin/ to whatever profile your terminal is set to use as the default.
Then enable this setting in vscode so it uses the same shell as your default terminal for running tasks:

"code-runner.runInTerminal": true

If you do like this you don't need to specifically change the path for every required externally installed app or extension.

ℹ️ In my case I needed to add export PATH=~/.local/bin/:$PATH to my ~/.zshrc since my default shell is zsh.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.