Repository navigation
Slow virtualenv activation in terminal #15719
Description
Issue Type: Bug
When opening a terminal, the source .venv/bin/activate command is issued too late. Most times I'm already writing another command and the result is:
- Venv activation not done.
- My command fails.
- Frustration.
- This is very rare but hypotetically possible: that I execute a command I didn't want, and something breaks.
A video to understand it:
Peek.19-03-2021.07-50.mp4
Extension version: 2021.3.658691958
VS Code version: Code 1.54.3 (2b9aebd5354a3629c3aba0a5f5df49f43d6689f8, 2021-03-15T10:55:24.277Z)
OS version: Linux x64 5.10.23-200.fc33.x86_64
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 4000) |
| GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: unavailable_off rasterization: disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | 1, 1, 1 |
| Memory (System) | 15.47GB (1.76GB free) |
| Process Argv | --no-sandbox --unity-launch --crash-reporter-id 1b07b1f6-f187-42fc-aa9e-516fd1a4c83e |
| Screen Reader | no |
| VM | 0% |
| DESKTOP_SESSION | gnome |
| XDG_CURRENT_DESKTOP | GNOME |
| XDG_SESSION_DESKTOP | gnome |
| XDG_SESSION_TYPE | x11 |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475
pythontb:30265425
vscoresta800cf:30276762
vspre833:30267464
vsdfh931:30275552
vshan820:30276952
Activity
karthiknadig commentedon Mar 22, 2021
Duplicate of #11039
firvida commentedon Jul 5, 2021
Have the exact same behavior in my computer, I can't see how this is a duplicated if #11039.
OS: Opensuse Leap 15.3 / Centos 8 / Manjaro
VSCode: 1.57.0
Extension version: v2021.7.992362372-dev
aleuyX commentedon Jul 23, 2021
I' ve had this issue since last update, same as described by Jairo Llopis (@yajo), takes quite a lot of time to load the virtual environment, and if you already started typing the source command fails, not loading the env at all. I don't see how this is a duplicate of #11039 either
I also notice some slowness in linting and formatting from about the same date this started happening
OS: KDE neon 5.22 (Ubuntu based kernel version 5.8.0-63-generic(64bits)
Vscode 1.58.2
Extension version: v2021.7.1053846006
I manually downgraded to v2021.6.944021595, this does not happen in that version. It seems to start from version 2021.7.1050252941
egorgam commentedon Aug 2, 2021
I have this behavior too. It's very frustrating sometimes
egorgam commentedon Aug 2, 2021
Jairo Llopis (@yajo) Abel Alfonso Fírvida Donéstevez (@firvida) Alejandro Sena (@aleuyX) there is alternative hack:
Put it in settings.json:
"python.terminal.activateEnvironment": false,
"terminal.integrated.env.osx": {"VENV_PATH": ".venv/bin/activate",}
and in END of ~./zshrc:
if [[ -n $VENV_PATH ]]; then
echo "Activating venv $VENV_PATH"
source $VENV_PATH
fi
Now venv is activating immediately when vscode terminal is open =)
PS: if you use windows or linux, use another terminal.integrated.env.* method.
PSS: if you use bash instead zsh, use .bachrc
firvida commentedon Aug 2, 2021
I use zsh too, so this is issue is maybe just for users which use zsh
yajo commentedon Aug 2, 2021
firvida commentedon Aug 2, 2021
Maybe a non bash users issue???