Skip to content
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

Old xesmf version dependency creates problems #2729

Closed
zklaus opened this issue Jul 20, 2022 · 0 comments · Fixed by #2728
Closed

Old xesmf version dependency creates problems #2729

zklaus opened this issue Jul 20, 2022 · 0 comments · Fixed by #2728

Comments

@zklaus
Copy link

zklaus commented Jul 20, 2022

The xesmf package has seen quite some development over the last years which involve much better dependency handling and a change of the project name on Pypi to pangeo-xesmf, though the Python package as well as the conda-forge package retain the old xesmf name.

We use xesmf in the UERRA cmorizer using an old API that was removed with the move to pangeo in 0.4.0, which keeps us stuck to the old version 0.3.0. To move to the newer versions, we should update the cmorizer, change our setup.py and lift/update the pinning.

bouweandela added a commit that referenced this issue Jul 21, 2022
Closes #2606
Closes #2299
Workaround for #2695
Closes ESMValGroup/ESMValCore#1364?

Versioning

    Use setuptools-scm to give a more accurate version number. The version number is built up as follows:
    {major}.{minor}.{patch}.dev{distance}+g{commit}+d{date}.
    Examples:
        For released versions, it will remain unchanged, e.g. 2.5.0
        If there are additional commits since the release, the patch version number will be increased with one and the number of commits since the release and the current commit will be used to generate a more detailed description. For example, if you are on v2.5.0 of the tool and there have been 72 commits in your current branch since that release and the latest commit has the (hexadecimal) number a424c89 (you can find the number of all commits in the current branch by using git log), then the version number will look like this: 2.5.1.dev72+ga424c891d.
        If there are uncommitted changes, the letter d and the current date will be added to the version number, e.g. 2.5.1.dev72+ga424c891d.d20220719

CircleCI

    Use appropriate resources
    Upload compressed artifacts for fast runs
    Upload test results in a format that CircleCI understands, enabling test summaries and statistics
    Only run documentation test nightly, readthedocs build is now configured to fail on warnings

Readthedocs

    Use mamba build
    Fail on warnings

Docker

    Use mamba container as a basis

Python development installation

    Install all development dependencies from conda-forge

R development installation

    Install all development dependencies from conda-forge

Stickler CI

    Remove the configuration file because we are not using this service anymore

Updates to dependencies

    Pin cf-units to a version that is compatible with the tests for the v2.6 release (Test failure due to change in cf-units ESMValCore#1655)
    Pin r-akima (recipe_miles_* broken due to newest akima package versions #2695)
    Pin xesfm to 0.3.0 (Old xesmf version dependency creates problems #2729)
    Remove xesmf dependency numba (Dependency refinement sparse, numba pangeo-data/xESMF#158)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants