I am having trouble getting VS Code to recognize a virtual environment. If you have any problems with VS Code recognizing a virtual environment, please file an issue in the documentation repository so we can help determine the cause. How do I get VS Code to keep using virtualenvs I create after I upgrade my homebrew python version? This is really annoying I don't want to keep recreating virtualenvs every time python updates (nor do I want to lock my homebrew system python from upgrading). Even manually specifying the interpreter in the user settings.json and the workspace settings.json file, VS Code keeps yelling about 'Select Python Interpreter.' It seems to have stopped believing that the virtualenv is valid. VS Code refuses to use the old virtualenv. 'Select Python Interpreter'Įven though I specified copy all files, even though I can workon vscode and that brings up the old 3.7.2 python virtualenv, all packages still installed, (1.3MB)īut: VS Code is no longer happy about the virtual environment. Removing: /Users/user/Library/Caches/Homebrew/python-pip-19.0.2.tar.gz.

Removing: /Users/user/Library/Caches/Homebrew/python-3.7.2.tgz.

Removing: /Users/user/Library/Caches/Homebrew/python-wheel-0.33.0.tar.gz. They will install into the site-package directory `python3`, `python3-config`, `pip3` etc., respectively, have been installed intoīrew install can install Python packages with

Unversioned symlinks `python`, `python-config`, `pip` etc.

=> /usr/local/Cellar/python/3.7.3/bin/python3 -s setup.py -no-user-cfg install -force -verbose -install-scripts=/usr/local/Cellar/

Visual studio code python virtualenv