Terminal shows venv activation

[ulugbekna]

Type: Bug

Behaviour

If I have a venv in my workspace folder, when I launch terminal, I see source /Users/ulugbekna/code/my-project/venv/bin/activate every time.

CleanShot.2025-02-18.at.14.38.29.mp4

Steps to reproduce:

1. Have a venv that's python extension interpreter set at
2. Create terminal - 🐛 see the source ...

(maybe I have some specific setup that causes this)

Diagnostic data

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

XXX

Extension version: 2025.1.2025021801
VS Code version: Code - Insiders 1.98.0-insider (e20adc378e7bda18152984725c31d22cb4eaac17, 2025-02-17T05:04:55.143Z)
OS version: Darwin arm64 24.3.0
Modes:

• Python version (& distribution if applicable, e.g. Anaconda): 3.13.0.final.0
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): System
• Value of the python.languageServer setting: Default

User Settings

languageServer: "Pylance"

Installed Extensions

Extension Name	Extension Id	Version
black-formatter	ms-	2024.6.0
Bookmarks	ale	13.5.0
codespaces	Git	1.17.3
copilot	Git	1.272.1380
copilot-chat	Git	0.25.2025021801
cpptools	ms-	1.23.6
debug-value-editor	ms-	0.1.0
debugpy	ms-	2025.1.2025021701
deoptexplorer-vscode	rbu	1.1.2
EditorConfig	Edi	0.17.0
errorlens	use	3.23.0
esbuild-problem-matchers	con	0.0.3
explorer	vit	1.14.1
extension-test-runner	ms-	0.0.12
fluent-icons	mig	0.0.19
gc-excelviewer	Gra	4.2.63
gitlens	eam	2025.2.1604
go	gol	0.44.0
graphviz-interactive-preview	tin	0.3.5
hexeditor	ms-	1.11.1
isort	ms-	2023.10.1
java	red	1.40.2025020508
js-debug-companion	ms-	1.1.3
js-debug-nightly	ms-	2025.2.1117
json-string-viewer	Ulu	0.0.3
jupyter	ms-	2025.2.2025020701
jupyter-keymap	ms-	1.1.2
jupyter-renderers	ms-	1.1.0
kusto	don	0.4.4
LiveServer	rit	5.7.9
npm-intellisense	chr	1.4.5
ocaml-platform	oca	1.28.0
prettier-vscode	esb	11.0.0
pretty-ts-errors	Yoa	0.6.1
python	ms-	2025.1.2025021701
rainbow-csv	mec	3.17.0
remote-containers	ms-	0.398.0
remote-explorer	ms-	0.5.2025021709
remote-repositories	ms-	0.43.2024112101
remote-server	ms-	1.6.2025010809
remote-ssh	ms-	0.118.2025021215
remote-ssh-edit	ms-	0.87.0
remote-wsl	ms-	0.88.5
remotehub	Git	0.65.2024112101
rust-analyzer	rus	0.3.2308
simulation-test-runner	ms-	0.0.4
svg-preview	Sim	2.8.3
template-string-converter	meg	0.6.1
test-adapter-converter	ms-	0.2.1
tldraw-vscode	tld	2.45.0
toggle	reb	0.0.2
ts-file-path-support	ms-	1.0.0
tsl-problem-matcher	amo	0.6.2
turbo-console-log	Cha	2.11.5
typescript-notebook	don	2.0.6
vscode-alternate-file	wil	0.3.1
vscode-azureresourcegroups	ms-	0.10.5
vscode-diagnostic-tools	ms-	1.2.0
vscode-docker	ms-	1.29.4
vscode-drawio	hed	1.8.250217011
vscode-eslint	dba	3.0.10
vscode-github-issue-notebooks	ms-	0.0.130
vscode-js-profile-flame	ms-	1.0.9
vscode-js-profile-table	ms-	1.0.10
vscode-jupyter-cell-tags	ms-	0.1.9
vscode-jupyter-slideshow	ms-	0.1.6
vscode-pull-request-github	Git	0.105.2025021804
vscode-pylance	ms-	2025.2.1
vscode-python-envs	ms-	0.3.10441011
vscode-speech	ms-	0.12.1
vscode-tree-sitter-query	jri	0.0.6
vscode-typescript-next	ms-	5.8.20250217
vscode-xml	red	0.28.2025021408
vscode-yaml	red	1.16.0
vsliveshare	ms-	1.0.5948
wasm-dwarf-debugging	ms-	1.0.1
web-editors	ms-	0.3.0
yaml-plus-json	hil	1.12.2

System Info

Item	Value
CPUs	Apple M1 Pro (8 x 2400)
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: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	4, 4, 5
Memory (System)	32.00GB (0.13GB free)
Process Argv	--log github.vscode-pull-request-github=debug --log github.copilot-chat=trace --crash-reporter-id 3184aec0-4b31-4764-bfb0-162155975430
Screen Reader	no
VM	0%

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
py29gd2263:31024238
c4g48928:30535728
vscrp:30624060
962ge761:30841072
dsvsc014:30777825
dsvsc015:30821418
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
pythonait:30973460
dwnewjupytercf:31046870
nativerepl1:31134653
pythonrstrctxt:31093868
nativeloc1:31118317
e80f6927:31120813
iacca1:31150324
notype1:31143044
dwcopilot:31158714
h409b430:31177054
c3hdf307:31184662
471b6256:31240254
6074i472:31201624
dwoutputscf:31238124
hdaa2157:31222309
copilot_t_ci:31222730
f27dg485:31233432
g012b348:31231168
jda6j935:31233686
copilothoveron:31237050
g941i948:31240199

[anthonykim1]

Hey @ulugbekna thanks for filing this.
In fact, this isnt a regression, this is the behavior you get if you opt out of the terminal env var activation experiment.
You are just seeing the activation command on your terminal instead of having the Python extension implicitly activate your environment (which happens in when you are opt into the terminal env var activation experiment).

You can try opting into the experiment if you want to stick to "not seeing the activation command", but we eventually plan to remove the terminal experiment. Here are some relevant reads: #24567 and feel free to contribute your ideas to #24759 :)

[ulugbekna]

@anthonykim1 thank you for getting back on this! I can't remember changing anything around env activation. How can I opt into this activation experiment again?