gridfm / gridfm/gridfm-graphkit

gridfm-graphkit 0.8.0rc1 has unsatisfiable dependency constraints (urllib3 vs gridfm-datakit)

Open
#81 1 comment 0 reactions 1 assignee View on GitHub

@romeokienzler is already working on this.

Since Jun 26, 2026.

Dominant language
Python
Stars
105
Forks
36
Avg merge
1d 8h
Merged PRs (30d)
9

Description

Summary

gridfm-graphkit==0.8.0rc1 declares dependencies that cannot be satisfied together. Every published version of the required gridfm-datakit is incompatible with 0.8.0rc1's urllib3 constraint or with PyPI in general.

Conflict

gridfm-graphkit==0.8.0rc1 requires:

  • gridfm-datakit>=1.0.2
  • urllib3>=2.6.0

But on PyPI:

  • gridfm-datakit 1.0.2 and 1.0.3 pin urllib3<2.0.0 — conflicts with urllib3>=2.6.0.
  • gridfm-datakit 1.0.4 depends on gridfm-datakit-winblock; sys_platform == 'win32', which is not published on PyPI, so the version cannot be installed on any platform that performs full resolution.

Result: no version of gridfm-datakit satisfies gridfm-graphkit==0.8.0rc1's own constraints.

Reproduce

Add to a pyproject.toml:

[project]
requires-python = ">=3.12,<3.14"
dependencies = ["gridfm-graphkit==0.8.0rc1"]

Then uv lock (or pip install) fails with:

Because gridfm-datakit>=1.0.2,<=1.0.3 depends on urllib3<2.0.0 ...
Because there are no versions of gridfm-datakit-winblock and gridfm-datakit==1.0.4
  depends on gridfm-datakit-winblock{sys_platform == 'win32'}, we can conclude that
  gridfm-datakit==1.0.4 cannot be used.
And because gridfm-graphkit==0.8.0rc1 depends on gridfm-datakit>=1.0.2 and
  urllib3>=2.6.0, we can conclude that gridfm-graphkit==0.8.0rc1 cannot be used.

Possible fixes

  • Publish gridfm-datakit-winblock to PyPI, or remove that dependency from gridfm-datakit 1.0.4, and/or
  • Release a gridfm-datakit that allows urllib3>=2.6.0, and/or
  • Relax urllib3>=2.6.0 in gridfm-graphkit to a range compatible with an installable gridfm-datakit.

Context

Hit while attempting to bump gridfm-graphkit from 0.0.7 to 0.8.0rc1 in IBM/algorithm-nexus. The previous torch-version conflict that motivated the bump is now resolved — thanks for that — but the package is currently uninstallable due to the above.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.