Skip to content

Drop the globus-compute-sdk<4.7 upper bound - #141

Merged
OwenPriceSkelly merged 1 commit into
mainfrom
owen/unpin-globus-compute-sdk
Sep 11, 2026
Merged

OwenPriceSkelly merged 1 commit into
mainfrom
owen/unpin-globus-compute-sdk

Conversation

@OwenPriceSkelly

Copy link
Copy Markdown
Member

Summary

  • Remove the <4.7 upper bound on globus-compute-sdk added in 0.9.2. It guarded against a stray print("Response string: ...") in Client.get_task; upstream has since made it logger.debug (verified in 4.16.0: globus_compute_sdk/sdk/client.py only logs it).
  • Re-lock: globus-compute-sdk 4.2.0 → 4.16.0, globus-sdk 3.65.0 → 4.9.0 (proxystore 0.8.3 → 1.1.0 came along).

Why now

The bound forces globus-sdk 3, so groundhog 0.9.2 cannot share an environment with anything that needs globus-sdk 4 — academy-py (0.5 and 1.0) in particular. Resolvers silently fall back to groundhog 0.9.1 for such scripts, which lacks everything merged since.

Not in this PR

requires-python <3.14 and the 3.14 import guard stay. Globus Compute SDK 4.15 added Python 3.14 support, so lifting that cap is a separate follow-up.

Test plan

  • uv run pytest (370 passed), uv run ruff check ., uv run ty check .
  • uv pip compile of academy-py>=1.0 + this branch resolves (GC SDK 4.16 / globus-sdk 4.9)

🤖 Generated with Claude Code

The bound was added in 0.9.2 to avoid a stray print("Response string: ...")
in Client.get_task that spammed stdout on every poll. Upstream has since
turned it into logger.debug (present as such in 4.16.0), so the bound only
blocks coexistence with packages that need globus-sdk 4 — notably academy-py,
which cannot be installed alongside groundhog 0.9.2 at all.

Lock moves to globus-compute-sdk 4.16.0 / globus-sdk 4.9.0. Tests, ruff and
ty pass unchanged.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@OwenPriceSkelly
OwenPriceSkelly merged commit b15dc4a into main Sep 11, 2026
2 checks passed
@OwenPriceSkelly
OwenPriceSkelly deleted the owen/unpin-globus-compute-sdk branch September 11, 2026 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant