The new python environment extension does not activate the environment when launching a task

[albertino87]

Before the introduction of the python environment extension whenever i was launching a vscode task the python env for that project was automatically activated. Now it doesn't seem to work anymore. this happens with the pre-release version of the python extension ans python-environments extension

[eleanorjboyd]

Hi! You should be able to see the old experience if you set the setting: "python-envs.terminal.autoActivationType": "shellStartup". Let me know if this fixes it for you

[albertino87]

No it does not, even after restarting VSCode, the setting is not even recognised.

Besides the Debugger is not working anymore, when I right-click on a test and click Debug:

This is my launch.json:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python Debugger: Current File",
            "type": "debugpy",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "justMyCode": false,
        },
        {
            "name": "Python Parallel",
            "type": "debugpy",
            "request": "launch",
            "program": "tests/",
            "console": "integratedTerminal",
            "args": [
                "-n", "4"
            ],
            "justMyCode": false,
        }
    ]
}

I don't know if the two things are related but approximately 5 weeks ago VsCode started giving me several issues, like not setting the environment variable in the .env file. Now it started again. I had to change the way I work. It was working perfectly before, env variables automatically loaded and python environment automatically activated when:

• opening the terminal
• running a vscode task
• debugging test and/or file
• running a test and/or file.

If it can help I'm using SSH remote from windows to Linux

[eleanorjboyd]

do you still have the python environments extension enabled and can you see the python icon in the sidebar? Also make you you are trying that setting at the user not workspace level:

[albertino87]

I did set the setting and restarted the application, but still no success, the environment is not activated:

[eleanorjboyd]

can you check your bash profile script and make sure you see something to includes vscode injected code? It should have something like #vscode to start and end the inserted block

[albertino87]

where is this bash script? i have never seen it and never touched any profile script. I use vscode with the remote ssh extension

[eleanorjboyd]

see https://github.com/microsoft/vscode-python-environments?tab=readme-ov-file#shell-startup-activation will help you find the profile. We do the injection so you don't have to touch the script.

Also wrote out this doc to help with debugging this and explaining shell activation: https://github.com/microsoft/vscode-python-environments/wiki/Terminal-Auto%E2%80%90Activation-Explained

[albertino87]

This is my .bashrc file:

# .bashrc

# Source global definitions
if [ -f /etc/bashrc ]; then
        . /etc/bashrc
fi

# User specific environment
if ! [[ "$PATH" =~ "$HOME/.local/bin:$HOME/bin:" ]]
then
    PATH="$HOME/.local/bin:$HOME/bin:$PATH"
fi
export PATH

# Uncomment the following line if you don't like systemctl's auto-paging feature:
# export SYSTEMD_PAGER=

# User specific aliases and functions

# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/var2/miniconda/bin/conda' 'shell.bash' 'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
    eval "$__conda_setup"
else
    if [ -f "/var2/miniconda/etc/profile.d/conda.sh" ]; then
        . "/var2/miniconda/etc/profile.d/conda.sh"
    else
        export PATH="/var2/miniconda/bin:$PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<


export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion
export PATH="$PATH:/opt/mssql-tools18/bin"

# >>> vscode python
# version: 0.1.1
if [ -z "$VSCODE_PYTHON_AUTOACTIVATE_GUARD" ]; then
    export VSCODE_PYTHON_AUTOACTIVATE_GUARD=1
    if [ -n "$VSCODE_BASH_ACTIVATE" ] && [ "$TERM_PROGRAM" = "vscode" ]; then
        eval "$VSCODE_BASH_ACTIVATE" || true
    fi
fi
# <<< vscode python

I see some vscode injected code

[albertino87]

So I am not sure how I am supposed to run my tasks based on my python environments anymore.
If I use the Shellstartup autoActivationType mechanism -> it has no effect compared to the Command autoActivationType
Let's take this simple task with the Command autoActivationType mechanism (after resetting the .bashrc file to the original state):

        {
            "label": "Format App",
            "type": "shell",
            "command": "ruff format --config ruff.toml",
        },

I get:

/bin/bash: ruff: command not found

 *  The terminal process "/bin/bash '-c', 'ruff format --config ruff.toml'" failed to launch (exit code: 127). 
 *  Terminal will be reused by tasks, press any key to close it. 

If I change the task to:

        {
            "label": "Format App",
            "type": "shell",
            "command": "conda activate en3.12 && ruff format --config ruff.toml",
        },

I get:

CondaError: Run 'conda init' before 'conda activate'

 *  The terminal process "/bin/bash '-c', 'conda activate en3.12 && ruff format --config ruff.toml'" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it. 

If I change the task to:

        {
            "label": "Format App",
            "type": "shell",
            "command": "conda init && conda activate en3.12 && ruff format --config ruff.toml",
        },

I get:

no change     /home/d608771/miniconda3/condabin/conda
no change     /home/d608771/miniconda3/bin/conda
no change     /home/d608771/miniconda3/bin/conda-env
no change     /home/d608771/miniconda3/bin/activate
no change     /home/d608771/miniconda3/bin/deactivate
no change     /home/d608771/miniconda3/etc/profile.d/conda.sh
no change     /home/d608771/miniconda3/etc/fish/conf.d/conda.fish
no change     /home/d608771/miniconda3/shell/condabin/Conda.psm1
no change     /home/d608771/miniconda3/shell/condabin/conda-hook.ps1
no change     /home/d608771/miniconda3/lib/python3.13/site-packages/xontrib/conda.xsh
no change     /home/d608771/miniconda3/etc/profile.d/conda.csh
no change     /home/d608771/.bashrc
No action taken.

CondaError: Run 'conda init' before 'conda activate'


 *  The terminal process "/bin/bash '-c', 'conda init && conda activate en3.12 && ruff format --config ruff.toml'" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it. 

In a normal bash console everything works just fine.