Pin uxarray-mcp to Python 3.12#61
Merged
Merged
Conversation
…ch failures A 3.13 submitter against a 3.12 endpoint worker raises WorkerLost on non-trivial payloads through Globus Compute's default serializer. The MCP tools survive simple round-trips via AllCodeStrategies but any user code dropping down to Executor.submit() will hit it. Until upstream lands a documented compatibility story (tracked at globus/globus-compute#2139), pinning the package to 3.12 matches the conda stacks that HPC sites ship today and keeps users out of WorkerLost territory. - pyproject.toml: requires-python = ">=3.12,<3.13"; classifiers reduced to 3.12. NOTE comment in the file explains why and points at the upstream issue so the next maintainer knows when to revisit. - .python-version: 3.13 → 3.12 so `uv run` and `uv sync` pick the right interpreter automatically. - README: install commands show `uv tool install --python 3.12`; new callout explains the constraint and links the upstream issue. - docs/remote-hpc.md: same pin in the HPC-extras install step. - docs/operating-an-endpoint.md: the worker-Python callout points at the upstream issue; the second conda-env example in the 8-step section bumped from python=3.11 to python=3.12 for consistency with the quickstart. - .github/workflows/ci.yml: matrix collapsed to 3.12; pre-commit, smoke, HPC, docs jobs all updated to 3.12. - .github/workflows/release.yml: build/install/verify steps updated to 3.12. - uv.lock: regenerated for the narrower requires-python (drops 3.11/3.13 dependency variants). Verified: - pre-commit clean - 295 tests pass under 3.12 (vs 290 under 3.13 — five cartopy-dependent tests that were skipped on 3.13 macOS now run) - sphinx -W --keep-going clean
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pin the package to Python 3.12 — `requires-python = ">=3.12,<3.13"` plus matching updates to install commands, docs, CI matrix, and `.python-version`. The pin is provisional, tracked at globus/globus-compute#2139 — the upstream issue I filed describing the underlying `WorkerLost` failure on submitter↔worker Python minor mismatch — and will be lifted once Globus Compute publishes a multi-version compatibility story.
Why
A 3.13 submitter against a 3.12 endpoint worker raises `WorkerLost` on non-trivial Globus Compute payloads. The packaged MCP tools survive simple dict-of-strings round-trips via `AllCodeStrategies` but any user code dropping down to `Executor.submit()` will hit pickle protocol skew. HPC sites (chrysalis, Casper, Improv) broadly ship Python 3.12 conda stacks today, so matching that on the submitter side is the path with fewest sharp edges. The `uxarray-mcp doctor` warning that landed in #60 catches mismatches at probe time, but we can avoid the mismatch in the first place for the install path we recommend.
Changes
Test plan
Notes