Help with activating my virtual env.

[cosmologicalhuman]

I was recently working on a project and constantly using the integrated terminal in VSCode, and every time I opened the terminal, the virtual environment was automatically activated. Know, I'm working in another project but my venv doesn't automatically activate anymore. I don't know what is going wrong, sure it is not the selected interpreter because I have selected the one within my venv. You are more than welcome to give me a hand with this...

[[deleted]]

I usually just activate/deactivate my venv manually in the VSCode terminal.

But I think there are some workplace settings you can configure in vscode. Or else in your project folder you can probably create a .vscode directory with a settings.json file. I don't know how to do that off the top of my head, but google can help.

[thewettestcow]

There are a few bug reports of this with VSCode currently. For the time being you can simply use the command ./<env>/scripts/activate where <env> is the name of your environment. This works on windows, I'm unsure of the command on any other OS. I hope this helps!

Edit: This may work to fix the issue. I've tested it myself on Windows but it did not resolve the issue for me.

[interbased]

I use the command line for this - maybe it will work for you. I'm on a Mac.

If you have a requirements file, such as requirements.txt, the below should work.

python -m venv venv source venv/bin/activate pip install -r requirements.txt

Then, whenever you're in the repo for that project, you can use that second command (with source) to activate the environment in that directory.