I know the original question was about conda under MacOS. But I would like to share the experience I've had on Ubuntu 20.04.
In my case, the issue was due to an alias defined in ~/.bashrc
: alias pip='/usr/bin/pip3'
. That alias was taking precedence on everything else.
So for testing purposes I've removed the alias running unalias pip
command. Then the corresponding pip
of the active conda environment has been executed properly.
The same issue was applicable to python
command.