Conda-build sets PIP_NO_BUILD_ISOLATION and PIP_NO_DEPENDENCIES (See https://github.com/conda/conda-build/blob/0ad4bb6829b440caae9ae8a4db14ab1ff3788ab7/conda_build/build.py#L3020). Why is it also being set in every recipe in
|
"<{ PYTHON }} -m pip install . -vv --no-deps --no-build-isolation" |
? There are other flags set by conda-build, so this seem like an arbitrary set to re-specify on the command line.
I think both1 of these should be removed to allow conda-build to specify everything needed for pip to work and keep the recipes as simple as possible. Or all the other flags should be added too.
Notice in conda-forge/packaging-feedstock#32 where --no-build-isolation was being added to a recipe based on greyskull.
Conda-build sets
PIP_NO_BUILD_ISOLATIONandPIP_NO_DEPENDENCIES(See https://github.com/conda/conda-build/blob/0ad4bb6829b440caae9ae8a4db14ab1ff3788ab7/conda_build/build.py#L3020). Why is it also being set in every recipe ingrayskull/grayskull/strategy/pypi.py
Line 67 in 5b29307
I think both1 of these should be removed to allow conda-build to specify everything needed for pip to work and keep the recipes as simple as possible. Or all the other flags should be added too.
Notice in conda-forge/packaging-feedstock#32 where
--no-build-isolationwas being added to a recipe based on greyskull.Footnotes
Not completely sure PIP_NO_DEPENDENCIES is the same as
--no-deps, as it seems to be it should bePIP_NO_DEPS. The translation is automatic, and there isn't a--no-dependenciesflag. But I am sure thatPIP_NO_BUILD_ISOLATIONis correct. So at least that one could be trimmed here. Edit: tested and PIP_NO_DEPENDENCIES does work ↩