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

"Linter pylint is not installed" when changing settings.json #260

Closed
Zvezdin opened this issue Nov 19, 2017 · 1 comment
Closed

"Linter pylint is not installed" when changing settings.json #260

Zvezdin opened this issue Nov 19, 2017 · 1 comment
Labels
area-linting bug Issue identified by VS Code Team member as probable bug

Comments

@Zvezdin
Copy link

Zvezdin commented Nov 19, 2017

Environment data

VS Code version:
1.18.1-1
Python Extension version:
0.8.0
Python Version:
3.6.3
OS and version:

Arch Linux x64

Actual behavior

When adding the following line to my user setings: "python.linting.pylintArgs": ["--disable=W0312"], I get an error message, that pylint is not installed (it is). If I remove the argument, so the line becomes "python.linting.pylintArgs": [], the error doesn't show up and linting works without problems.

Outside of VSCode, running python -m pylint testscript.py --disable=W0312 works as expected.

Expected behavior

Pylint should work with that one warning disabled. VSCode shouldn't throw that error, since it is misleading and incorrect.

Steps to reproduce:

Have VSCode install pylint for you. Add "python.linting.pylintArgs": ["disable=W0312"] to your user settings.

Logs

Output from Python output panel

Linting with pylint failed.
You could either install the 'pylint' linter or turn it off in setings.json via "python.linting.pylintEnabled = false".
Error: spawn pylint ENOENT

Output from Console window (Help->Develop

Linter pylint is not installed (messageService.ts:126)

e.doShow | @ | messageService.ts:126
-- | -- | --
  | e.show | @ | messageService.ts:105
  | e._showMessage | @ | mainThreadMessageService.ts:72
  | n.Class.derive._oncancel | @ | winjs.base.raw.js:1641
  | e._showMessage | @ | mainThreadMessageService.ts:42
  | e.$showMessage | @ | mainThreadMessageService.ts:36
  | e.invoke | @ | abstractThreadService.ts:41
  | e._invokeHandler | @ | rpcProtocol.ts:109
  | e._receiveOneMessage | @ | rpcProtocol.ts:96
  | (anonymous) | @ | rpcProtocol.ts:32
  | (anonymous) | @ | rpcProtocol.ts:157
  | e.invoke | @ | callbackList.ts:36
  | e.fire | @ | event.ts:123
  | (anonymous) | @ | ipc.net.ts:82
  | emitOne | @ | events.js:96
  | emit | @ | events.js:191
  | readableAddChunk | @ | _stream_readable.js:178
  | Readable.push | @ | _stream_readable.js:136
  | onread | @ | net.js:560
@DonJayamanne
Copy link

Duplicate of #42

@DonJayamanne DonJayamanne marked this as a duplicate of #42 Nov 19, 2017
@DonJayamanne DonJayamanne added awaiting 4-validation area-linting bug Issue identified by VS Code Team member as probable bug labels Nov 19, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-linting bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants