Closed gmacgilchrist closed 12 months ago
Thanks for posting here
Hey @aaronspring,
I think I'm running into the same issues as well with the conda package for climpred
. I get the impression that the core dependencies of it may be stale/obsolete? My theory is that it might have something to do with the netcdf4
/libnetcdf
used to generate the last conda package: https://github.com/CSHS-CWRA/RavenPy/pull/278#issuecomment-1561765243 (for clarity, v0.2.0 of raven-hydro
is much newer than v3.6; we're changing things up for that package).
What's interesting though is that older versions of climpred
seem to install fine for me. It only arrives with climpred>=2.2.0
.
I can see in the recipe that the more recent versions added a few new dependencies:
xclim
(definitely not the problem, the maintainers are beautiful geniuses ;) )xesmf
esmpy =*=mpi*
My workaround for the time being is to install everything I need for climpred
via conda/mamba
, then install climpred
from PyPI.
Would it make sense to try publishing a new release/build to see what the problem might be?
a new conda release, see https://github.com/conda-forge/climpred-feedstock/pull/23 any more suggestions what to change are welcome
With my newfound maintainer powers, I just released an updated climpred
conda-forge package that removes the esmpy
pin. It appears to be installing without any issues alongside my other dependencies!
@gmacgilchrist Can you verify that the latest build works for you? Let us know here!
see https://github.com/conda-forge/climpred-feedstock/issues/26 and #832 hopefully resolving
Is this now closed by https://github.com/conda-forge/climpred-feedstock/pull/27? @gmacgilchrist
Sorry for the delay in checking this. This works with the new build. Thank you.
It seems as though dependencies of
climpred
version2.3.0
are incompatible with the latest version ofpython
(3.11
). This appears to be rooted in the fact thatnumba
requirespython<=3.10
. This can cause problems if installingclimpred
in an environment that has pinnedpython=3.11
or installing directly from anenvironment.yml
file in which no versions are specified andpython=3.11
is picked up by default. In those cases,climpred
reverts to version1.1.0
!The only approach that I found that worked was to set up a completely clean environment, and a call to install only
climpred
, i.e.Some things that failed that might help pin down the dependency issues
An install with
python=3.9
installs on old version ofnumba
(0.53.1
), as well as other older dependencies. This is likewise true for an install that attempts to forceclimpred=2.3.0
. Importingclimpred
with these environments fails with the following Traceback, which again points to difficulties withnumba
:It is possible that an
environment.yml
file that specifiespython=3.10
would work. I didn't have time to try.I think I have now sorted this problem with a clean install, but I am posting here for reference. This is obviously an upstream issue, relating to
numpy
dependencies. However, it may be worthwhile putting some further information with the installation instructions that highlights these potential problems.Many thanks for eveeryone's work on this package - it's a tremendous resource.