Skip to content

Dependency conflict with new xarray packages #113

Open

Description

@rushin682

Hi Paul,

I noticed, the new xarray package versions (i.e >=2025.0) tends to have conflicts with several dependencies when 'pip' installer when installing HEST. The conflicts are easily resolved with the UV package manager but issues are when using pip. I tried several different changes on 3 clusters. Restricting xarray is the only solution I came up with. Maybe this could be helpful.

pyproject.toml.txt

To reproduce:
Install HEST as is in a conda env now. You get several dependency conflicts

error: resolution-too-deep

× Dependency resolution exceeded maximum depth
╰─> Pip cannot resolve the current dependencies as the dependency graph is too complex for pip to solve efficiently.

hint: Try adding lower bounds to constrain your dependencies, for example: 'package>=2.0.0' instead of just 'package'. 

Solution: Update toml file with "xarray<=2024.11"

Lmk if this works for you and should be updated.

Activity

  1. SophieSarceau commented on Aug 13, 2025

    @SophieSarceau

    I used GPT5 to help me update the pyproject.toml file, and successfully downloaded the HEST on my server.

    Image

    pyproject.toml.txt

  2. pauldoucet commented on Aug 31, 2025

    @pauldoucet
    Collaborator

    Hi @rushin682, @SophieSarceau,
    Thanks for reporting this issue! I was able to reproduce the error. It seems that #114 solved it without adding an upper bound for xarray. Let me know if the problem persists and I'll add your suggested changes if needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions