Open mhshen opened 4 months ago
+1 also running into this issue starting last week
After mode debugging, this is due to an interaction between my packagemanager and vscode-cli in particular. Only triggered when opening vscode from terminal. Most likely due to the fact that a virtualenv is already engaged and the integrated terminal is inherited.
After debugging a python/C++ project, I created a new zsh window in vscode, and conda environment fails to activate with the following error message.