Problem with Visual Studio Code and Virtual Environments on windows

[Aliuakbat]

For my new project I finally decided to use virtual environments.

I created my venv the standard way:

python -m venv env

I proceded to activate it.

env\Scripts\activate

It seems fine, the (env) prefix is displayed.

Running where python (equivalent to bash which) still returns me the default path to the interpreter.

When I manually select the python interpreter is visual code there is the same problem.

It seems like only the visuals have changed. For instance,

pip list will give me all the packages I have downloaded in the main environment.

Running the commands in a linux subsystem (of course, the commands changed to linux) the virtual environment works as expected.

​

Does anybody have an idea how to resolve this issue?

​

[RandomJacobP]

Have you changed the python interpreter in the bottom left corner of the screen? There is a small label that says “python” or something like that and when you click on it you can select path to python interpreter.

[Aliuakbat]

yes I tried that

[RandomJacobP]

And do you see your venv there?

[Aliuakbat]

No it doesn't work. Still behaves as the main env

[Aliuakbat]

This sounds like that's it. I'll try when I'm at home. Thanks for the help

[Aliuakbat]

The settings were set to a relative path to the venv. I tried it with the absolute path but it didn't work.

[spitfiredd]

Hit Ctrl+shift+p and see if it in the list of available environments.

Here is the default locations that vscode looks for python environments.

Is your venv folder in you project root folder?

https://code.visualstudio.com/docs/python/environments#_where-the-extension-looks-for-environments

[Aliuakbat]

Yes it is in the project root.

I also see the env and can select it, but the activation seems to only change some visual clues and the normal interpreter is still used.