Also ask pip not to install build dependencies during editable install when using conda #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).