Activation of virtual environment does not work when pyenv is installed

[DonJayamanne]

• OS: mac, but linux should be the same
• VS Code Insiders and latest pre-release version of Python ext
• Install pyenv
• Sedtup auto activation of terminals with Python environment
• Create a .venv in your worksapce folder
• Open a terminal either manually or using the command palette Python: Create Terminal
• run the command which python in the terminal
• The output is not the .venv environment, instead it points to pyenv

[karrtikr]

Unable to reproduce on codespaces, there're a lot of things that could be going on, primary thing to check is if shell integration is enabled and working.

Automatic shell integration may not work in remote scenarios: https://code.visualstudio.com/docs/terminal/shell-integration#_automatic-script-injection, manual installation maybe required.

Please provide the debug logs which can help diagnose the issue:

• Run Developer: Set log level command
• Select Trace
• Run Developer: Reload Window command
• Provide the output:

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

[DonJayamanne]

Automatic shell integration may not work in remote scenarios:

that’s complicating things
I’m not using remote, it’s pure desktop

[DonJayamanne]

Perhaps a Linux vm or Wsl would be better
Else you just run into unknowns and issues

as you have pointed out there could be issues with remote

shell integration is enabled

yes enabled
When I disable pyenv, activation start working

[karrtikr]

I would need the logs to further diagnose the issue, unable to reproduce on either Windows or codespaces.

[DonJayamanne]

When you setup pyenv, does it work in codespace terminal?

[karrtikr]

Yep:

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!