`pip install -e` installs the source under the current working directory instead of under the environment directory about berryconda

[Chong-Jiao]

How can I uninstall it if I install it by "pip install -e ."?

[ksze]

This is what pip install --help has to say about installing editable projects:

--src <dir>                 Directory to check out editable projects into. The default in a virtualenv is "<venv path>/src". The default for global installs is "<current dir>/src".

I also made sure that I'm running pip in the conda environment:

~ $ which pip
/home/ksze/berryconda3/envs/foobar/bin/pip

This suggests that pip somehow doesn't recognize a conda environment as a proper virtualenv.

However, you would probably agree that, for all intents and purposes, a conda environment activated by source activate foobar should be treated like a proper virtualenv. The question is how to make pip recognize it.

[jjhelmus]

Unfortunately conda environments are not virtualenv and therefore pip install -e results in the default behavior of installing into the current working directory. I agree that it would be nice if conda and virtualenv were more aware of each other. This is not an issue specific to berryconda, the same behavior is seen when using conda on other platforms. Opening issues upstream with with pip, virtualenv or conda would be a better place to discuss this topic.

[mrjamescollins]

'pip uninstall '
you can get this name by doing a 'pip list'