VSCode 1.96.0 with GitHub CoPilot Extension enabled Breaks Activation of Python venv in Terminal

[scottbisker]

Type: Bug

When the GitHub Copilot Extension is enabled, Terminals with associated Python venv do not activate the venv. This happened after upgrading to 1.96.0 today using debian package from https://packages.microsoft.com/repos/code

1. Create Python .venv
2. Enable GitHub Copilot Extension
3. Activate terminal with .venv
4. Terminal appears activated with (.venv) prefix, however, attempting to run deactivate does not work as it is not in the path. Other path modifications for virtual environment are not present.
5. Disable GitHub Copilot Extension
6. Activate new terminal with .venv
7. Terminal is activated and running deactivate works as expected.

Attempted downgrading Github Copilot Extension version to three previous releases and still broken.

VS Code version: Code 1.96.0 (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Linux x64 6.9.3-76060903-generic
Modes:

System Info

Item	Value
CPUs	12th Gen Intel(R) Core(TM) i7-12700H (20 x 3982)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off webnn: disabled_off
Load (avg)	1, 2, 1
Memory (System)	62.64GB (46.62GB free)
Process Argv	--crash-reporter-id 4b1e7378-92bb-4be7-8c73-92d5dcb567d3
Screen Reader	no
VM	0%
DESKTOP_SESSION	pop
XDG_CURRENT_DESKTOP	Unity
XDG_SESSION_DESKTOP	pop
XDG_SESSION_TYPE	x11

Extensions (36)

Extension	Author (truncated)	Version
vscode-django	bat	1.15.0
npm-intellisense	chr	1.4.5
vscode-markdownlint	Dav	0.57.0
vscode-eslint	dba	3.0.10
python-environment-manager	don	1.2.4
python-extension-pack	don	1.7.0
copilot	Git	1.249.0
copilot-chat	Git	0.23.1
remotehub	Git	0.64.0
vscode-pull-request-github	Git	0.102.0
vsc-python-indent	Kev	1.18.0
vscode-docker	ms-	1.29.3
debugpy	ms-	2024.14.0
isort	ms-	2023.10.1
python	ms-	2024.22.0
vscode-pylance	ms-	2024.12.1
jupyter	ms-	2024.11.0
jupyter-keymap	ms-	1.1.2
jupyter-renderers	ms-	1.0.21
vscode-jupyter-cell-tags	ms-	0.1.9
vscode-jupyter-slideshow	ms-	0.1.6
remote-containers	ms-	0.394.0
remote-ssh	ms-	0.116.0
remote-ssh-edit	ms-	0.87.0
remote-wsl	ms-	0.88.5
vscode-remote-extensionpack	ms-	0.26.0
azure-repos	ms-	0.40.0
remote-explorer	ms-	0.4.3
remote-repositories	ms-	0.42.0
remote-server	ms-	1.5.2
autodocstring	njp	0.6.1
vetur	oct	0.37.3
vscode-xml	red	0.27.2
vscode-yaml	red	1.15.0
vim	vsc	1.29.0
jinja	who	0.0.8

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
vscrp:30673768
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

[scottbisker]

Downgrading the package to the following version resolves the issue.

code_1.95.3-1731513102

[karthiknadig]

@scottbisker Can you share the logs from Output > Python? Also when you are created the terminal did you use any command from the python-environment-manager extension ?

[scottbisker]

In troubleshooting, I removed the python environments and then recreated using Python: Create Environment. I selected the correct Python version and the environment was created. Nothing special was done to create the environments. And this issue applies to all Python virtual environments. VSCode is even creating a pop-up notification that the virtual environment is now activated, when it is in fact not. I don't have any output from Output->Python.

…

On Thu, Dec 19, 2024 at 11:40 AM Karthik Nadig ***@***.***> wrote: @scottbisker <https://github.com/scottbisker> Can you share the logs from Output > Python? Also when you are created the terminal did you use any command from the python-environment-manager extension ? — Reply to this email directly, view it on GitHub <#24643 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI247JLHNDJZSTC4QE4GPJT2GLZGTAVCNFSM6AAAAABT5MEMOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJVGAYDAMZQGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[karthiknadig]

@scottbisker Add this setting to your user settings, and Re-load.

    "python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"]

You may also need to run Python: Clear cache and reload window command after updating the setting. See if that helps.

[scottbisker]

Thanks! By adding that setting, the terminal now activates the virtual environment as expected.

…

On Thu, Dec 19, 2024 at 1:22 PM Karthik Nadig ***@***.***> wrote: @scottbisker <https://github.com/scottbisker> Add this setting to your user settings, and Re-load. "python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"] You may also need to run Python: Clear cache and reload window command after updating the setting. See if that helps. — Reply to this email directly, view it on GitHub <#24643 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI247JKNJKSOAUQ4PZKPXDL2GMFERAVCNFSM6AAAAABT5MEMOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJVGQ4TSOBYGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>