If you pip install -e . when using conda, any missing dependencies are installed by pip. You can avoid that by passing --no-deps to the pip command. (pyctdev ecosystem=conda installs all deps using conda, so --no-deps just avoids pip checking all the deps and finding them all present.)
With pip now supporting build dependencies, we should also ask pip not to install the build dependencies when we're using conda. Otherwise, pip will spend time creating an isolated environment and installing all the build dependencies before running setup.py, which is at best a waste of time (as the dependencies are already available, from conda). (At worst, there could be some subtle problem or conflict, although I haven't encountered that in practice yet.)
I don't know when the 'no build isolation' option appeared - not sure if I missed it originally, or if it wasn't present in the pip of that era (also not sure if pip was installing build deps back then).
If you
pip install -e .when using conda, any missing dependencies are installed by pip. You can avoid that by passing--no-depsto the pip command. (pyctdev ecosystem=conda installs all deps using conda, so--no-depsjust avoids pip checking all the deps and finding them all present.)With pip now supporting build dependencies, we should also ask pip not to install the build dependencies when we're using conda. Otherwise, pip will spend time creating an isolated environment and installing all the build dependencies before running setup.py, which is at best a waste of time (as the dependencies are already available, from conda). (At worst, there could be some subtle problem or conflict, although I haven't encountered that in practice yet.)
I don't know when the 'no build isolation' option appeared - not sure if I missed it originally, or if it wasn't present in the pip of that era (also not sure if pip was installing build deps back then).