How to integrate with Visual Studio Code?

[victorwoo]

In Windows 11, I opened the PowerShell terminal and entered some commands to create a local Python environment called env_name. I used the pyenv-win-venv commands like this:

pyenv-win-venv install 3.8.5 env_name
pyenv-win-venv activate env_name
pyenv-win-venv local env_name

Then, I opened Visual Studio Code. I pressed Ctrl + Shift + P to bring up the command palette and selected Python: Select Intepreter. But I didn't see the env_name interpreter in the list.

However, when I used pyenv-virtualenv commands instead:

pyenv local 3.12.7
pyenv shell 3.12.7
virtualenv -p3.12.7 env_name

Visual Studio Code could recognize this new environment. And in the Python: Select Intepreter option, there was a new entry Python 3.12.7 ('env_name': venv).\env_name\Scripts\python.exe. So, I'm wondering how to make pyenv-win-venv work properly with Visual Studio Code just like virtualenv does.

[harryeffinpotter]

I, too, have issues with using this lib with VSCode, in my scenario i created my virtualenv, which was all good, and then I set the init to take place in my powershell profile, which worked as well.

But now when I go to debug I get the

& was unexpected at this time...

error.

I discovered this is because for whatever reason, this library uses CMD. Whenever the virtualenv is initialized it swaps over to CMD and then the debugging lines no longer work. Insanely frustrating. The repo has powershell commands to install it but the wrapper forces CMD? JUST WHY.