You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Virtual environment without activate script does not respect python.terminal.activateEnvironment setting #22898
When selecting a Python virtual environment that has no bin/activate script (but has a pyvenv.cfg), then the Python extension will ignore the python.terminal.activateEnvironment setting and always prepend the venv bin directory to path.
Expected
When python.terminal.activateEnvironment=false, then the PATH is not changed (as happens with a regular python venv)
Steps to reproduce:
Set python.terminal.activateEnvironment to false
Run python -m venv venv
Remove venv/bin/activate
Open a new integrated terminal and check the terminal environment changes
Diagnostic data
Python version (& distribution if applicable, e.g. Anaconda): 3.10.12
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
Value of the python.languageServer setting: Default
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Extension version: 2024.0.1
VS Code version: Code 1.86.1 (31c37ee8f63491495ac49e43b8544550fbae4533, 2024-02-07T09:07:19.849Z)
OS version: Linux x64 6.1.0-1033-oem
Modes:
Connection to 'SSH: llruicms01' could not be established Canceled
Remote OS version: Linux x64 6.1.0-1033-oem
Théo Cuisset (@tcuisset) Can you check on the latest insider version of Python extension that you are having the same problem? It is likely resolved by #22909
Activity
karrtikr commentedon Feb 13, 2024
Please provide the debug logs which can help diagnose the issue:
Developer: Set log levelcommandTraceDeveloper: Reload WindowcommandOutput for
Pythonin theOutputpanel (View→Output, change the drop-down the upper-right of theOutputpanel toPython)anthonykim1 commentedon Mar 29, 2024
Théo Cuisset (@tcuisset) Can you check on the latest insider version of Python extension that you are having the same problem? It is likely resolved by #22909