Pip: `pip install -e` does not treat a conda environment like a proper virtualenv.
- Pip version: 9.0.1
- Python version: 3.6.2
- Operating system: Raspbian Jessie
Description:
I wanted to install some packages in editable mode (pip install -e) in a conda environment. I expected the source files to appear in <env name>/src, but they ended up in the current working directory.
What I've run:
You can see the details in the corresponding conda ticket (https://github.com/conda/conda/issues/5861).
I'm cross posting the issue so that both project teams are aware and can discuss what's the best approach to resolve this.
ksze
All 2 comments
I don't think we'd be adding a special case for conda in pip's virtual environment detection logic.
@kalefranz Is it possible for conda to appropriately modify its environment to look like a virtual environment?
pradyunsg
on 20 Jul 2019
In particular, core Python now has sys.base_executable, with "being in a virtual environment" being identifiable by sys.base_executable != sys.executable. If conda were to work with that, it would follow core Python standards, and would automatically be recognised by pip (as well as by any other tool that neededto know if it was running in a virtual environment).
pfmoore
on 20 Jul 2019
Related issues
therefromhere
路
3Comments
yizhang-zen
路
3Comments
wrouesnel
路
3Comments
dmfigol
路
3Comments
jiapei100
路
3Comments
Most helpful comment
In particular, core Python now has
sys.base_executable, with "being in a virtual environment" being identifiable bysys.base_executable!=sys.executable. If conda were to work with that, it would follow core Python standards, and would automatically be recognised by pip (as well as by any other tool that neededto know if it was running in a virtual environment).