Open rsignell opened 1 month ago
@kthyng I guess an update is then needed in cmocean?
Oof, turns out cmocean fixed this problem a year ago, but for some reason I didn't get that version -- I have cmocean=2.0
in the environment I just built. I need to figure out which package in my environment is pinning that...
I think that same realization process happened to me in my opendrift environment! I ending up deciding it might be OpenDrift's requirements, although I have read about poetry's notation and I don't think it should be that based on what it said. From my recollection though, in my env OpenDrift was the only package pinning cmocean at all at 2.0. I ended up updating the package locally in my env and moving on without saying anything since I wasn't sure that was the problem
Aha! https://github.com/conda-forge/opendrift-feedstock/blob/main/recipe/meta.yaml#L32 (@ocefpaf found this)
BTW, inspecting opendrift's dependencies, many of them looks like optional deps. Maybe those should be listed as such to make it easier people to install it?
Of course @ocefpaf figures it out! Good thinking to look there.
I updated to cmocean>=3.0
, which is hopefully ok?
https://github.com/conda-forge/opendrift-feedstock/blob/main/recipe/meta.yaml#L32
@knutfrode If you are using numpy 2.0 you'll probably need v.3.1.3
to get the release correct because it always takes me a few releases to get everything right... https://github.com/matplotlib/cmocean/releases. I have cmocean set up differently than my other packages and always mess it up.
OpenDrift presently pins numpy<2.0
since adios_db (oil library) is not yet adapted to numpy 2. This might be updated within a couple of months.
Should I anyway change to cmocean>=3.1.3
right away?
Yes I think that is a good idea.
Ok, this is now updated.
I updated to
cmocean>=3.0
, which is hopefully ok? https://github.com/conda-forge/opendrift-feedstock/blob/main/recipe/meta.yaml#L32
Please see my comment in https://github.com/conda-forge/opendrift-feedstock/commit/6fa5d0b6f10161d3e076b60bc5133013350f725e#r144694960
and https://conda-forge.org/docs/maintainer/updating_pkgs/#forking-and-pull-requests for more info.
Note that a new package was notcreated. The problem persists for those using conda-forge and it requires a build number bump to fix it.
Using the latest packages from conda-forge,
fails with
Looks like the problem is here: https://github.com/matplotlib/matplotlib/issues/28349
I took the "easy route" of pinning matplotlib to 3.7.3