Skip to content

fix(pyproject): correct torch ppc64le/s390x exclusion comment - #265

Draft
ashokponkumar wants to merge 2 commits into
torch-spyre:mainfrom
ashokponkumar:fix-torch-ppc64le-s390x-marker
Draft

fix(pyproject): correct torch ppc64le/s390x exclusion comment#265
ashokponkumar wants to merge 2 commits into
torch-spyre:mainfrom
ashokponkumar:fix-torch-ppc64le-s390x-marker

Conversation

@ashokponkumar

Copy link
Copy Markdown
Collaborator

Summary

  • Corrects the comment on the ppc64le/s390x torch exclusion marker to accurately describe the mechanism: torch-spyre now provides torch on ppc64le via its own uv git-source override (from-source build), so hf-adapters doesn't need a wheel from this dependency there; s390x has no upstream wheel or from-source path at all.
  • Regenerated uv.lock to match (no functional dependency change; the torch>=2.0; platform_machine not in 's390x, ppc64le' marker itself is unchanged from the prior fix).

Test plan

  • uv lock regenerated cleanly against the corrected comment (no logic change)
  • Verified as part of the broader torch-spyre ppc64le uv-source-override fix (companion PRs in torch-spyre and spyre-frameworks)

torch-spyre now sources torch via a uv git-source override on ppc64le
(from-source build), so hf-adapters doesn't need its own +cpu wheel
there; s390x has neither an upstream wheel nor a from-source override,
so torch is unresolvable there regardless. Regenerated uv.lock to match.

Signed-off-by: Ashok Pon Kumar <ashokponkumar@gmail.com>
@ashokponkumar
ashokponkumar marked this pull request as draft July 31, 2026 17:41
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