Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

algorithm-nexus[product]==0.2.2 broken on fresh pip install: torchgeo 0.10.0 incompatibility

Closed Beginner friendly
  • Is something wrong?
#213 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
build-system

Research direction

Inspect the [product] dependency declaration and requirements-product.txt, then reproduce the failure with the clean pip install and the terratorch import command. Compare the unlocked dependency resolution with the working torchgeo<0.10 workaround and upstream compatibility status. Done means a fresh algorithm-nexus[product]==0.2.2 install completes and the vLLM plugin and Terratorch registration imports succeed.

Written by the indexing model from the issue text.

Description

Summary

A fresh pip install algorithm-nexus[product]==0.2.2 fails at runtime because pip resolves torchgeo==0.10.0, which is incompatible with the pinned terratorch[vllm]==1.2.10.

Error

ImportError: cannot import name 'utils' from 'torchgeo.trainers'
(/opt/vllm/lib64/python3.12/site-packages/torchgeo/trainers/__init__.py)

This breaks both the terratorch_fix vLLM plugin and the Terratorch model architecture registration, making geospatial models (e.g. ibm-nasa-geospatial/Prithvi-EO-2.0-300M-TL-Sen1Floods11) unservable via vLLM.

Root Cause

  1. torchgeo 0.10.0 (released 2026-08-14) renamed torchgeo.trainers → torchgeo.tasks (torchgeo PR #3887). The trainers.utils submodule was not shimmed with a deprecation alias — it was simply removed.

  2. terratorch 1.2.10 (the version pinned by algorithm-nexus) imports from torchgeo.trainers import utils in multiple files (timm_model_factory.py, cli_tools.py, base_task.py, reconstruction_tasks.py, wxc_downscaling_task.py). Its pyproject.toml declares torchgeo as a dependency with no upper bound.

  3. algorithm-nexus 0.2.2 pins terratorch[vllm]==1.2.10 in the [product] extra but has no direct torchgeo version constraint. The requirements-product.txt lock file pins torchgeo==0.9.0, but a bare pip install algorithm-nexus[product]==0.2.2 (without the lock file) lets pip resolve torchgeo==0.10.0, which breaks the import.

Upstream Status

  • terratorch PR #1222 (merged 2026-08-18 to main) pins torchgeo>=0.9.0,<0.10 — but this fix is not in any release. Latest release is still v1.2.10 (2026-07-15), which predates the fix.
  • terratorch PR #1221 (open) does a full API migration to support torchgeo 0.10.

Reproduction

# In a clean environment or container (e.g. quay.io/vllm/automation-vllm:cuda-*)
pip install algorithm-nexus[product]==0.2.2

# This fails:
python -c "from terratorch.vllm.plugins.general import register_terratorch_fix"
# ImportError: cannot import name 'utils' from 'torchgeo.trainers'

# Workaround:
pip install "torchgeo<0.10"
# Now the import succeeds
Dominant language
Python
Stars
4
Forks
7
Avg merge
19h 13m
Merged PRs (30d)
20

Getting set up

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.

More from IBM/algorithm-nexus

All issues in IBM/algorithm-nexus

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.