-
Notifications
You must be signed in to change notification settings - Fork 353
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 update -f <file>.yml
ignores pip dependencies
#2221
Comments
Interesting. So you'd expect that we call |
Yes, I think this is how conda and mamba behave (though I am not entirely sure about the |
The same behavior is observed when using |
@peanutfun can you please check what's Conda's behavior here? |
Here is the mamba output:
Similar command for the same environment run via |
@avarganov I think there are other tickets open for this issue. If not, please open a new one |
@avarganov The issue you are referring to is tracked here: #2008 @jonashaag Conda and Mamba both install pip dependencies when executing |
Do they run |
@jonashaag Yes, seems to me like they always run |
Thanks! If you want to come up with a fix I'm happy to help |
As far as I understand, the |
Should this line be removed https://github.com/mamba-org/mamba#installing-lock-files from README.md until the new release when the bug is fixed? In it's current state the documentation is misleading since conda-lock does account for pip installations |
Is there any update on this? This prevents a nice interplay between |
Maybe one of the commenters here has the time to come up with an initial patch? |
Any updates on this?
The confusing thing is that the output does state it installs the pip package:
but at the end, one tiny line hints to the failure:
In this case, as the .yml contained only one pip package, it is clear but it was not with many pip packages. What is the workaround here? |
This has been fixed in #3419 which has been first distributed in mamba 2.0. |
Troubleshooting docs
Search tried in issue tracker
#2008 mentions that pip dependencies are not exported, so there might be an underlying issue with handling pip dependencies
Latest version of Mamba
Tried in Conda?
Not reproducible with Conda
Describe your issue
YAML spec files may specify dependencies that are to be installed using
pip
instead ofconda
/mamba
/micromamba
. Unlikeconda
andmamba
,micromamba
ignores these dependencies when callingmicromamba update
.Two exemplary environment specs:
Steps to replicate:
mamba info / micromamba info
Logs
environment.yml
~/.condarc
No response
The text was updated successfully, but these errors were encountered: