Run selection (shift+enter) sends code to terminal before python interpreter is activated

[Lauler]

Hi

In the last few months I have had an issue with run selection (shift + enter) that has been difficult for me to debug and fix. When selecting code and pressing Shift + Enter I expect i) the correct virtual environment to activate (in this case conda), ii) Python interpreter to activate, iii) the selected code to be sent to python interpreter in terminal and be executed.

A couple of months ago my VSCode began executing these in the incorrect order.

1. Activate conda environment
2. Send the selected code to terminal
3. Activate the python interpreter for the environment

or

1. Send selected code to terminal
2. Activate conda environment
3. Activate python interpreter for the environment.

With python.terminal.activateEnvrionment: true:

faton@faton ~/.../text/sprakpolisen >  
faton@faton ~/.../text/sprakpolisen > from dotenv import load_dotenv  
zsh: command not found: from
faton@faton ~/.../text/sprakpolisen > conda activate sprakpolisen  
(sprakpolisen) faton@faton ~/.../text/sprakpolisen >   
(sprakpolisen) faton@faton ~/.../text/sprakpolisen > /home/faton/miniconda3/envs/sprakpolisen/bin/python                                         git:main*
Python 3.10.13 (main, Sep 11 2023, 13:44:35) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
Ctrl click to launch VS Code Native REPL
>>>

Sometimes the order of execution is different:

conda activate sprakpolisen
from src.translate import translation_preprocess                                                                                                           
faton@faton ~/.../text/sprakpolisen > conda activate sprakpolisen                                                                                         
(sprakpolisen) faton@faton ~/.../text/sprakpolisen > from src.translate import translation_preprocess                                                     
zsh: command not found: from
(sprakpolisen) faton@faton ~/.../text/sprakpolisen >                                                                                             git:main*
(sprakpolisen) faton@faton ~/.../text/sprakpolisen > /home/faton/miniconda3/envs/sprakpolisen/bin/python                                         git:main*
Python 3.10.13 (main, Sep 11 2023, 13:44:35) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
Ctrl click to launch VS Code Native REPL
>>>

I have tried toggling a bunch of different settings. Among them "python.terminal.activateEnvironment" and "python.terminal.activateEnvInCurrentTerminal".

The only thing that sort of works is if I set both of the above to false. If I do this then:

1. Python interpreter is activated
2. Selected code is sent to terminal.

faton@faton ~/.../text/sprakpolisen >  
faton@faton ~/.../text/sprakpolisen > /home/faton/miniconda3/envs/sprakpolisen/bin/python  
from dotenv import load_dotenv
Python 3.10.13 (main, Sep 11 2023, 13:44:35) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
Ctrl click to launch VS Code Native REPL
>>> from dotenv import load_dotenv

But this of course sacrifices auto-activating python environments when starting a terminal.

Do you have any suggestions for settings I can try, and how I can go about to debug this? I tried uninstalling Python Environments extension, but it had no effect.

Info:

Version: 1.103.0
Commit: e3550cfac4b63ca4eafca7b601f0d2885817fd1f
Date: 2025-08-06T21:40:10.271Z
Electron: 37.2.3
ElectronBuildId: 12035395
Chromium: 138.0.7204.100
Node.js: 22.17.0
V8: 13.8.500258-electron.0
OS: Linux x64 6.8.0-65-generic

[eleanorjboyd]

Hi! Please check out this wiki I just wrote as I think the "shellStartup" setting for the Python Environments Extension might be what you are looking for: https://github.com/microsoft/vscode-python-environments/wiki/Terminal-Auto%E2%80%90Activation-Explained

[Lauler]

Thanks for the suggestion and wiki. Note: The activation of python environment works fine whenever I open a new terminal without sending any "run selection" code. However, when a new zsh terminal is opened as a result of a "run selection" (Shift + Enter) being triggered, the selected code is injected before the python interpreter is activated. This only happens when "python.terminal.activateEnvironment": true, and only happens when zsh is my default terminal.

• I tried changing the default shell from zsh to bash and it turns out that it works fine with bash. Unfortunately, with zsh it injects the code before the python interpreter is active -- no matter what I do.
• I tried Command (default), and Shell Startup Activation (making sure to add the relevant snippet to my .zshrc. Unfortunately code is submitted before python interpreter is active in both cases.

I will answer the questions at the end of the wiki:

• Shell type (Bash, Zsh, PowerShell, Command Prompt, Fish): Zsh
• OS (Windows/macOS/Linux): Linux
• Environment type (venv, Conda, Pipenv, etc.): Conda
• Auto-Activation Type setting value (Command / Command Shell Startup / Off): I tried all settings
• Expected behavior: Python interpreter should be activated before code sent via "run selection" is injected. This should be the behavior in all shells and regardless of the setting of "python.terminal.activateEnvironment".
• Actual behavior: With zsh as default terminal and "python.terminal.activateEnvironment": true, code sent via "run selection is injected before python interpreter is active. When using bash as default terminal, everything works as normal, even with "python.terminal.activateEnvironment": true.

If Command mode:
Activation command injected by VS Code:
VS Code correctly activates the environment if I open a new zsh terminal via the +-button or via Terminal -> New Terminal.

faton@faton ~/.../text/sprakpolisen > conda activate sprakpolisen  
(sprakpolisen) faton@faton ~/.../text/sprakpolisen >

However, when a new zsh terminal is opened as a result of Shift+Enter run selection, then "python.terminal.activateEnvironment": true causes the selected code to be injected before the python interpreter is activated in zsh:

conda activate sprakpolisen
faton@faton ~/.../text/sprakpolisen > conda activate sprakpolisen                                                                                                        
^C%                                                                                                                                                                       
faton@faton ~/.../text/sprakpolisen > import pandas as pd  
^C%                                                                                                                                                                       
faton@faton ~/.../text/sprakpolisen > /home/faton/miniconda3/envs/sprakpolisen/bin/python  
Python 3.10.13 (main, Sep 11 2023, 13:44:35) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
Ctrl click to launch VS Code Native REPL

Activation command that works outside VS Code: conda activate sprakpolisen (but this is not the issue).

Whether the issue happens in only one shell or multiple shells

Only happens in zsh. Works fine in bash.

Whether it reproduces after Reload Window and opening a fresh terminal

Yes, I reloaded the window and restarted VSCode after any settings changes.

I think I will change to bash as the default shell. But this might be a bug with VSCode + zsh. I would appreciate if someone could try to reproduce.

1. Use zsh as default shell.
2. ``"python.terminal.activateEnvironment": true`
3. Select a line of python code and Shift+Enter.
4. Is code injected before python interpreted is activated?