Shell integration isn't enabled for Task terminals

[karrtikr]

Creating based on #204694 (comment).

Context: Python extension uses environment collection to activate all terminals, via shell integration.

Some users launch certain apps via tasks microsoft/vscode-python#22880, expecting environment to be activated, and hence are failing because shell integration isn't active for such terminals.

A couple of solutions we could go with:

• Enable shell integration for task terminals, similar to how we're doing for debug terminals: Shell integration isn't enabled for Debug terminals #204694
• If shell integration isn't available for a terminal type, fallback on applying environment collection using process creation instead. That is, if both "applyAtShellIntegration" and "applyAtProcessCreation" are set to true and shell integration is working, we only apply it at shell integration, otherwise we fallback to only apply it at process creation.

[Jean7667]

I have the same problem

I tried that with no success:
{
"version": "2.0.0",
"tasks": [
{
"label": "Activate Virtual Environment",
"type": "process",
"command": "/usr/bin/zsh",
"args": [
"-c",
"source /mypathtomy/.virtualenvs/abc_app_3.12_virt_env/bin/activate && echo 'Virtual environment activated.'"
],
"problemMatcher": [],
"runOptions": {
"runOn": "folderOpen"
},
"presentation": {
"reveal": "always",
"panel": "shared",
"showReuseMessage": false
}
}
]
}
I tried with Type set to process or shell and I had the same result the tasks is triggered on startup, a new terminal is running with the task but the virtualenv is not activated in this terminal.
I would expect that the task runs in the current terminal and that the virtual env is activated at the end of the execution.
Looking at the documentation it does not seem to have a setting for that.

https://stackoverflow.com/questions/78430426/automating-activate-python-virtualenv-with-visual-studio-task-does-not-work

Problem with
VSCODE Version: 1.89.0
Commit: b58957e
Date: 2024-05-01T02:08:25.066Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Linux x64 6.5.0-28-generic

[Tyriar]

No plan to do this any time soon.

cc @anthonykim1

[keplerk]

Not sure if this can "help" a bit, but what I did was to directly use the "executable" right out of the scripts folder, and that helped in my case, maybe someone else can benefit of this workaround. (I'm on Windows)

[ldeluigi]

Please re-open this feature request