You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Activating a venv when opening a terminal takes 3-4 seconds. Previously, it used to be pretty much instantaneous. Even worse, while the env is being activated, I can already run commands, which eventually will error because they require the activated env.
Steps to reproduce:
Open the integrated terminal
Observe the "Activating venv" message in the toolbar
This takes a few seconds
After that, the venv is finally activated
Extension version: 2026.5.2026070801
VS Code version: Code 1.130.0 (Universal) (1b6a188127eeaf9194f945eb6eb89a657e93c54c, 2026-07-22T14:55:04Z)
OS version: Darwin arm64 25.5.0
Modes:
Python version (& distribution if applicable, e.g. Anaconda): 3.14.5
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
This issue also prevents users from properly running a Python script via the "Run Python File" toolbar button. When no previous terminal exists, the script starts before the environment is activated, so it uses the global Python environment instead of the virtual environment (typically resulting in errors). So I would say this is a pretty serious issue...
Could this be related to some newly introduced VS Code setting? It seems like the environment gets activated only after the message disappears after a few seconds:
Setting "terminal.integrated.initialHint": false removes the message, but not the delay!
Activity
[-]Activating environment suddenly take 3-4 seconds[/-][+]Activating environment suddenly takes 3-4 seconds[/+][-]Activating environment suddenly takes 3-4 seconds[/-][+]Activating environment suddenly takes a few seconds[/+][-]Activating environment suddenly takes a few seconds[/-][+]Activating environment takes a few seconds[/+]cbrnr commentedon Jul 30, 2026
This issue also prevents users from properly running a Python script via the "Run Python File" toolbar button. When no previous terminal exists, the script starts before the environment is activated, so it uses the global Python environment instead of the virtual environment (typically resulting in errors). So I would say this is a pretty serious issue...
cbrnr commentedon Jul 31, 2026
Could this be related to some newly introduced VS Code setting? It seems like the environment gets activated only after the message disappears after a few seconds:
Setting
"terminal.integrated.initialHint": falseremoves the message, but not the delay!cbrnr commentedon Sep 23, 2026
I tried to replicate this issue with 1.138.0, and it seems it was fixed at some point.