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
Since latest Linux version don't support installing apps with pip (except --break-system-packages), I have a base environment on uv (similar to conda).
My .bashrc:
# ---------------------------# Python env auto-activation (uv)# ---------------------------# Clean up inherited but inactive python environments (e.g. VSCode parent process env leakage)if [ -n"$VIRTUAL_ENV" ] &&!declare -F deactivate >/dev/null;then
PATH=$(echo ":$PATH:"| sed "s|:$VIRTUAL_ENV/bin:|:|g"| sed "s|^:||; s|:$||")export PATH
unset VIRTUAL_ENV
fiif [ -x"$PWD/.venv/bin/python" ];then
deactivate 2>/dev/null ||truesource"$PWD/.venv/bin/activate"elseif [ -z"$VIRTUAL_ENV" ];thensource~/.local/share/uv/environments/base/bin/activate
fifi
With this, extension doesn't work well and even though it says .venv is selected, it's not.
Screencast.from.2026-03-02.12-21-44.webm
I care about a base environment for tests so is there a way of support?
Since latest Linux version don't support installing apps with pip (except
--break-system-packages), I have a base environment on uv (similar to conda).My
.bashrc:With this, extension doesn't work well and even though it says .venv is selected, it's not.
Screencast.from.2026-03-02.12-21-44.webm
I care about a base environment for tests so is there a way of support?