forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
area-lintingbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugverifiedVerification succeededVerification succeeded
Milestone
Description
Environment data
- VS Code version: 1.33.1
- Extension version (available under the Extensions sidebar): 2019.4.12954
- OS and version: Debian Buster all updates applied
- Python version (& distribution if applicable, e.g. Anaconda): 3.7 from official Debian repositories
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
- Relevant/affected Python packages and their versions: XXX
Expected behaviour
Just install pylint once in a new venv.
Actual behaviour
Vsc always tries to reinstall pylint even if it is already installed.
Steps to reproduce:
- Set "python.pythonPath": in workspace settings.json, so that you use a venv which is not in the root of the workspace folder.
- Open a Python file, modify it and save the changes. Every time you save the Python file, vsc will warn you and suggets to reinstall pylint, even if it is already successfully installed.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area-lintingbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugverifiedVerification succeededVerification succeeded

