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
Solution to issue cannot be found in the documentation.
I checked the documentation.
Issue
Several users have reported problems (xgcm/xgcm#494xgcm/xgcm#492) which go back to a bug in xgcm v0.7.0 (incorrect dependencies). This should have been fixed by #13.
There is a new build (pyhd8ed1ab_1) available which has the correct dependencies (python >=3.9), but when users try to install xgcm with python 3.8 conda will resolve to the earlier faulty build.
Code to reproduce:
mamba create -n test -c conda-forge python=3.8 xgcm=0.7
I think the cleaneast solution woud be to remove build pyhd8ed1ab_0 for v0.7.0 from conda-forge (which hopefully would lead conda to resolve to 0.6.x instead of 0.7.0), but I am not sure how to do it and if it is a huge hassle.
I made an attempt to patch the metadata here. I think this is the more desirable fix, since the package data itself was fine, just the conda-forge metadata was wrong.
Was it on automerge? Lately I'm avoiding that and regenerating the recipes with grayskull to ensure the upstream metadata is in the recipe. It really helps avoid this kind of situation.
No I think I was just overly excited about the new xgcm version and messed up manually.
Lately I'm avoiding that and regenerating the recipes with grayskull to ensure the upstream metadata is in the recipe. It really helps avoid this kind of situation.
Thats super helpful advice. Ill try to keep that in mind for future releases.
Solution to issue cannot be found in the documentation.
Issue
Several users have reported problems (xgcm/xgcm#494 xgcm/xgcm#492) which go back to a bug in xgcm v0.7.0 (incorrect dependencies). This should have been fixed by #13.
There is a new build (
pyhd8ed1ab_1
) available which has the correct dependencies (python >=3.9), but when users try to install xgcm with python 3.8 conda will resolve to the earlier faulty build.Code to reproduce:
mamba create -n test -c conda-forge python=3.8 xgcm=0.7
results in:
I think the cleaneast solution woud be to remove build
pyhd8ed1ab_0
for v0.7.0 from conda-forge (which hopefully would lead conda to resolve to 0.6.x instead of 0.7.0), but I am not sure how to do it and if it is a huge hassle.cc @ocefpaf
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: