Closed yurivict closed 1 year ago
@yurivict could you show the output of xarray.show_versions()
? I suspect you are using an old version of cftime. Xarray requires a minimum version of 1.5.
(Obviously the above comment only applies if cftime installed; technically cftime is an optional dependency)
$ pkg info | grep cftime
py39-cftime-1.0.3.4_1 Time-handling functionality from netcdf4-python
requirements.txt doesn't have cftime in it.
(Obviously the above comment only applies if cftime installed; technically cftime is an optional dependency)
But if it breaks when a wrong cftime version is present you probably should check its version and not use it or fail when it is too old.
I think the problem is that there is no way to pin optional dependecies in conda. I understand your frustration but it's not practical to explicitly test for all of this in the code.
Oh apparently you can place constraints on optional packages: https://docs.conda.io/projects/conda-build/en/latest/resources/define-metadata.html#run-constrained
Seems like we just need to update the meta.yaml
in the feedstock appropriately.
What happened?
There are many failures due to missing 'daysinmonth' attribute:
Version: 2023.1.0 Python-3.9 FreeBSD 13.1
What did you expect to happen?
No response
Minimal Complete Verifiable Example
No response
MVCE confirmation
Relevant log output
No response
Anything else we need to know?
No response
Environment