no-config debugger can't detect conda env

[Chuong98CC]

when using the no-config debugger recently released in version 1.97.2, i can't get the debugger working with conda env.
it keeps using the default base env:
in the debug console, i check for the current env:

import sys
sys.executable
'/home/linuxbrew/.linuxbrew/opt/python@3.13/bin/python3.13'

my conda env is settup using python select intepretter, and in terminal, it automatically select the correct env, but not with debugpy

Here are the other screenshots that I tried all the recommended setting found on the wiki page

[karthiknadig]

@Chuong98CC Can you share what binaries you have in the conda environment? If I remember correctly, debugpy command tries to run python3, it assumes that environment managers add python3 in the environment. My guess is that the environment has only python executable.

[Chuong98CC]

My conda env uses Python 3.10. Can you elaborate how to check for the binary files?

[karthiknadig]

Try running this from a terminal:

> conda run -n <envname> python -c "import sys; print(sys.executable)"

It should print eh path to the executable (similar to the script in your comment above). go to the directory containing the executable, and run ls | grep python

[Chuong98CC]

thanks @karthiknadig
here is the screenshot

[Chuong98CC]

@karthiknadig @eleanorjboyd any update on this issue

[karthiknadig]

@Chuong98CC In the case where it is broken can you run echo $PATH in the terminal. From the terminal output I can't tell if the environment is activated or not. Basically internally we run python -m debugpy .... , from the what you have shared, it looks like the python that is set on PATH is wrong. This means either the environment is not activated or something else is broken.

Share the output of following commands:

> echo $PATH
> whereis python3
> whereis python

[Chuong98CC]

It does not work. My conda env is "trackon"
In terminal, i checked all the path and they are correct.

But when I run "debugpy", in the debug console, it still recognize different python path

[Chuong98CC]

ok, so we have to add the path explicitly at the beginning of $PATH then it will work:

export PATH=/home/chuong/miniconda3/envs/trackon/bin:$PATH
debugpy tools/infer_pointtrack.py --vid_path $video

[karthiknadig]

The way PATH is setup, python3 and Python have different values in your environment. That is what is breaking this. We use python3 by default . This seems like something is broken in the way environments activated by conda. Those paths must be same.

@eleanorjboyd i cases where we can detect environment activation we should use python as a mitigation.