Skip to content

Pylint not working in virtual Environment in VS code #11964

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
eduzen opened this issue May 23, 2020 · 1 comment
Closed

Pylint not working in virtual Environment in VS code #11964

eduzen opened this issue May 23, 2020 · 1 comment
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@eduzen
Copy link

eduzen commented May 23, 2020

Environment data

  • VS Code version: Version: 1.45.1
  • Extension version (available under the Extensions sidebar): 2020.5.80290
  • OS and version: macos Catalina, 10.15.4
  • Python version (& distribution if applicable, e.g. Anaconda): python 3.8
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): .virtualenv
  • Jedi or Language Server?: Language Server
  • Value of the python.languageServer setting: XXX

Expected behaviour

I saw this issue #7620 and it happens also to me. Pylint doesn't work when is inside of venv. I have my settings.json:

{
    "python.venvPath": "~/.virtualenvs/eduzen/bin/python",
    "python.pythonPath": "~/.virtualenvs/eduzen/bin/python",
    "python.linting.pylintPath": "~/.virtualenvs/eduzen/bin/pylint",
    "python.linting.enabled": true,
    "python.linting.pylintEnabled": true,
}

If I specify another path for pylint like ~/.pyenv/shims/pylint works.

@eduzen eduzen added triage-needed Needs assignment to the proper sub-team bug Issue identified by VS Code Team member as probable bug labels May 23, 2020
@karthiknadig
Copy link
Member

This is dupe of #7314

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label May 27, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 16, 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