-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[micromamba] 0.21.0 breaks PIP_
config env variables
#1468
Comments
PIP_
config env variables
I suppose this is more directly related to #1413. |
Hi @austin1howard thanks for letting us know. I think it totally makes sense to run the pip command with a pass-through environment so that all env variables are inherited. |
PIP_
config env variablesPIP_
config env variables
I've tagged this with |
yeah seems so, I'm able to install through "regular" |
I know it's trivial but I pushed a PR to remove that line. |
Thanks! |
In
Mambamicromamba 0.21.0, environment variables starting withPIP_
(used to configure pip for things like extra indexes, etc.) are being stripped. I think this is part of #1422, in particular this change: wolfv@61c5de7#diff-ebac1cb6982f8e508ff9d8203d56f74aa3da80115d7ca84cc525a131ef23535aR61There may be good reason to suppress some environment variables, but this line's change only applies to running pip (or in the future some other third party package manager) so I don't think it makes sense to empty the environment variables. At least, env vars which start with
PIP_
should be passed through.The text was updated successfully, but these errors were encountered: