You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was working on a multi-output recipe (with pep517 backend, which hardcodes --ignore-installed, but I don't know if that's relevant) and noticed pip was downloading all dependencies again for both build and run requirements. This shouldn't happen as it results in clobber warnings because PREFIX ends up with vendored dependencies.
Expected Behavior
Pip should not download dependencies, as it happens with toplevel, single-output recipes.
Intended behaviour can be regained if the environment variables set in this function are passed manually, as shown here.
Actual Behavior
I was working on a multi-output recipe (with pep517 backend, which hardcodes
--ignore-installed
, but I don't know if that's relevant) and noticed pip was downloading all dependencies again for both build and run requirements. This shouldn't happen as it results in clobber warnings because PREFIX ends up with vendored dependencies.Expected Behavior
Pip should not download dependencies, as it happens with toplevel, single-output recipes.
Intended behaviour can be regained if the environment variables set in this function are passed manually, as shown here.
Steps to Reproduce
See conda-forge/napari-feedstock#29.
Output of conda info
The text was updated successfully, but these errors were encountered: