Selecting interpreter in VS Code does not activate environment
I am working with a conda environment that contains multiple packages, and I am trying to debug a Python script that calls those packages via shell commands. While selecting interpreter via VS Code uses that environment’s packages, it does not allow me to use the packages installed directly via conda.
Selecting interpreter in VS Code does not activate environment
I am working with a conda environment that contains multiple packages, and I am trying to debug a Python script that calls those packages via shell commands. While selecting interpreter via VS Code uses that environment’s packages, it does not allow me to use the packages installed directly via conda.
Selecting interpreter in VS Code does not activate environment
I am working with a conda environment that contains multiple packages, and I am trying to debug a Python script that calls those packages via shell commands. While selecting interpreter via VS Code uses that environment’s packages, it does not allow me to use the packages installed directly via conda.
Selecting interpreter in VS Code does not activate environment
I am working with a conda environment that contains multiple packages, and I am trying to debug a Python script that calls those packages via shell commands. While selecting interpreter via VS Code uses that environment’s packages, it does not allow me to use the packages installed directly via conda.
Selecting interpreter in VS Code does not activate environment
I am working with a conda environment that contains multiple packages, and I am trying to debug a Python script that calls those packages via shell commands. While selecting interpreter via VS Code uses that environment’s packages, it does not allow me to use the packages installed directly via conda.
VS Code not selecting correct conda environment for py but works for ipynb
I have a workspace with a .py
and a .ipynb
file. After I’ve selected the correct conda environment (py39llm
) VS Code keeps working with the base conda environment in the case of .py
but switches to the selected python environment for ipynb
: