-
Notifications
You must be signed in to change notification settings - Fork 6
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
Weirdly hard to install a simple pure-python plugin #108
Comments
Why we use conda, not mamba in bundle? |
(Seems like that should be a different issue @Czaki ;) |
👆 and I asked this so I could check whether mamba/micromamba would give different results here. btw afaik conda now uses libmamba to solve so the solve should not yield different results. I don't know whether I'm right about this though. |
My solution for such problem in the past was to switch from conda to mamba (and now I will think about try pixi). |
Hm, those logs are coming from the classic solver. Unclear why... Can you paste the output of:
|
|
I think I know why: the base env in the installer is being solved with Additionally, we are not finding |
napari/packaging#187 is the fix, ready for review. You can see the |
If I'm reading that correctly, affinder uses python 3.10 as minimum and bundle 3.9? |
That's a separate issue, I think. We can of course bump it up, but let's collect feedback about it first. @jni, the packaging fix is up. What to do next:
|
I have added 0.5.4rc4 to create ne release |
@jaimergp let's definitely bump Python though, 3.9 is ancient! I'd go for 3.11 or 3.12 these days. |
See napari/packaging#189 and let's discuss policy there. |
In the process of testing the napari 0.5.4rc3 macOS bundle, I tried to install affinder. Conda is still going so I'm making this issue asynchronously while that's going. It's unclear whether it's going to finish. 😂 But anyway, here's the list of affinder dependencies:
https://github.com/conda-forge/affinder-feedstock/blob/c16758e7b4cde7303aba68096c216a75e4b7fca5/recipe/meta.yaml#L25-L31
These are all things that should be satisfied a priori by the bundle, I believe? But the solve takes forever, then fails:
I await the result of the conflicts analysis and will update here when it's completed.
Is it easy to inspect what the package specification is for the bundle?
The text was updated successfully, but these errors were encountered: