Shell startup activation only works when creating terminal from env extension.

[anthonykim1]

Testing #340

Note virtual env was created using python -m venv .venv
Powershell Windows ARM)

It seems like shell startup activation method only works when creating terminal from the icon in the env extension panel.

If I were to create a terminal from elsewhere, such as via ctrl+shift+backtick, it would not create activated terminal.
Is this expected?

Screen.Recording.2025-04-28.at.2.19.58.PM.mov

Same story for Gitbash on Windows ARM:

Screen.Recording.2025-04-28.at.2.24.36.PM.mov

[karthiknadig]

Do you see contributions on the terminal tab for the various environments?

[anthonykim1]

Contributions when I open terminal (via regular control+shift+backtick) -> Gitbash:

# Terminal Environment Changes

## Extension: ms-python.debugpy

Enables use of [no-config debugging](https://github.com/microsoft/vscode-python-debugger/wiki/No%E2%80%90Config-Debugging), `debugpy <script.py>`, in the terminal.

- `DEBUGPY_ADAPTER_ENDPOINTS=c:\Users\anthonykim\.vscode-insiders\extensions\ms-python.debugpy-2025.0.1-win32-x64\.noConfigDebugAdapterEndpoints\endpoint-1c153c1d272361e2.txt`
- `PATH=${env:PATH};c:\Users\anthonykim\.vscode-insiders\extensions\ms-python.debugpy-2025.0.1-win32-x64\bundled\scripts\noConfigScripts`
- `BUNDLED_DEBUGPY_PATH=c:\Users\anthonykim\.vscode-insiders\extensions\ms-python.debugpy-2025.0.1-win32-x64\bundled\libs\debugpy`
- `PYDEVD_DISABLE_FILE_VALIDATION=1`

## Extension: GitHub.copilot-chat

Enables use of the `copilot-debug` command in the terminal.

- `PATH=${env:PATH};c:\Users\anthonykim\AppData\Roaming\Code - Insiders\User\globalStorage\github.copilot-chat\debugCommand`

## Extension: vscode.git

Enables the following features: git auth provider

- `GIT_ASKPASS=c:\Users\anthonykim\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\extensions\git\dist\askpass.sh`
- `VSCODE_GIT_ASKPASS_NODE=C:\Users\anthonykim\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe`
- `VSCODE_GIT_ASKPASS_EXTRA_ARGS=`
- `VSCODE_GIT_ASKPASS_MAIN=c:\Users\anthonykim\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\extensions\git\dist\askpass-main.js`
- `VSCODE_GIT_IPC_HANDLE=\\.\pipe\vscode-git-d725d66089-sock`

Now I'm getting same Contributions when pressing on teminal icon from env manager panel as well. (venv is no longer activated when launching terminal from env panel) now.

Screen.Recording.2025-04-28.at.2.37.26.PM.mov

[anthonykim1]

Note that I created virtual environment by typing
python3 -m venv .venv inside my terminal

[anthonykim1]

Now I'm getting venv activated when I open terminal in normal way (ctrl+shift+backtick) and also when pressing terminal icon on env panel.
I haven't changed anything, other than reloading vscode. not sure what is causing this flakiness.

Screen.Recording.2025-04-28.at.2.44.33.PM.mov

[karthiknadig]

This might still be a bug in the extension. I will need to investigate.

[anthonykim1]

I think the consistent repro for me (Windows ARM gitbash):

1. delete all virtual env on repo
2. Create one via terminal with python -m venv .venv
3. create terminal with normal keybinding (ctrl+shift+backtick) ---> venv not initialized
4. create terminal with create terminal UI from env manager panel ---> venv not intiailized

If I do Python Clear Cache and Reload:
Then I end up with:

• venv when clicking create terminal UI from env manager panel
• But no venv when creating terminal normally.