Python is in a Conda environment, but it has not been activated in a Windows virtual environment

The error message tells you that the Python interpreter from the Conda environment was found, but that conda activate <envname> has not been called. Did you put the bin/ directory of the Conda environment into the Windows search path? That would be wrong.

You’re talking about virtualenvs. But Python virtual environments are something else than Conda environments. Maybe you mixed up the two concepts?

The Python interpreter from the Conda base environment does not complain about missing activation, because it’s called by some of the conda subcommands and can work without an activated environment. Nevertheless, you should call conda activate base when working with that Conda environment, too.

Leave a Comment