Skip to content

pylint not running when language service is pylance or Microsoft #15672

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

Closed
RobertBaruch opened this issue Mar 16, 2021 · 1 comment
Closed

pylint not running when language service is pylance or Microsoft #15672

RobertBaruch opened this issue Mar 16, 2021 · 1 comment
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@RobertBaruch
Copy link

Environment data

  • VS Code version: 1.54.2
  • Extension version (available under the Extensions sidebar): v2021.2.636928669
  • OS and version: Windows_NT x64 10.0.19041
  • Python version (& distribution if applicable, e.g. Anaconda): 3.8.5
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
  • Relevant/affected Python packages and their versions: N/A
  • Relevant/affected Python-related VS Code extensions and their versions: N/A
  • Value of the python.languageServer setting: pylance or Microsoft

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

Expected behaviour

pylint runs

Actual behaviour

pylint does not run

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

  1. Create a Python file.
  2. Set language server to pylance or Microsoft. (Python > Language Server)
  3. Enable Python linting (Python > Linting: Enabled)
  4. Enable linting via pylint. (Python > Linting: Pylint Enabled)
  5. Ensure pylint is installed.
  6. Enable lint on save. (Python > Linting: Lint On Save)
  7. Open the Output window with Python selected.
  8. Save the file.
  9. Note that pylint is not run, as shown in the output.
  10. Change language server to Jedi
  11. Reload the window
  12. Save the file.
  13. Note that pylint is run.

Logs

@RobertBaruch RobertBaruch added triage-needed Needs assignment to the proper sub-team bug Issue identified by VS Code Team member as probable bug labels Mar 16, 2021
@karthiknadig
Copy link
Member

This is expected. Language Servers JediLSP, Pylance and Microsoft report problems themselves. To avoid collisions pylint is disabled by default when using any of these LS. You can explicitly enable pylint from settings, if you want to use it along with LS.

Duplicate of #7314

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Mar 16, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants