Skip to content

cuda.core: fix invalid python_version target in pixi.toml#2029

Merged
rparolin merged 1 commit into
NVIDIA:mainfrom
rparolin:fix/cuda-core-pixi-strenum-target
May 12, 2026
Merged

cuda.core: fix invalid python_version target in pixi.toml#2029
rparolin merged 1 commit into
NVIDIA:mainfrom
rparolin:fix/cuda-core-pixi-strenum-target

Conversation

@rparolin
Copy link
Copy Markdown
Collaborator

@rparolin rparolin commented May 5, 2026

Summary

  • cuda_core/pixi.toml had [package.target.'python_version < "3.11"'.run-dependencies], but pixi only accepts platform identifiers in [package.target.<X>]. Every pixi run against this manifest failed at parse time:
    × 'python_version < "3.11"' is not a known platform.
    
  • Move backports.strenum into the unconditional [package.run-dependencies]. Conda-forge ships per-Python variants (real impl gated to python <3.11, plus a 1.3.1 stub gated to python >=3.12), so the solver picks the right build per workspace.build-variants Python (3.10–3.14).
  • Lockfile regenerated; backports.strenum-1.3.1 now appears in the relevant environments.

Why this slipped in

No CI workflow currently runs pixi, so the broken stanza was never validated. Worth a follow-up to add a pixi task list smoke check, but out of scope here.

Test plan

  • pixi task list --manifest-path cuda_core/pixi.toml — manifest parses
  • pixi run --manifest-path cuda_core -e default test3039 passed, 178 skipped, 2 xfailed
  • pixi run test from repo root — 3026 passed, 187 skipped, 2 xfailed

🤖 Generated with Claude Code

Pixi's [package.target.<X>] only accepts platform identifiers; the
'python_version < "3.11"' selector caused every pixi invocation against
cuda_core/pixi.toml to fail at manifest-parse time
('python_version < "3.11"' is not a known platform).

Move backports.strenum into [package.run-dependencies] unconditionally
and let conda-forge's per-Python variants (real impl on <3.11, no-op
stub on >=3.12) handle version selection. Lockfile regenerated.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@rparolin rparolin added this to the cuda.core next milestone May 5, 2026
@rparolin rparolin added bug Something isn't working packaging Anything related to wheels or Conda packages cuda.core Everything related to the cuda.core module labels May 5, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 5, 2026

Copy link
Copy Markdown
Contributor

@mdboom mdboom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine for pixi. Wouldn't want to ship this metadata in any package we ship, but fine for local use.

@rparolin rparolin self-assigned this May 6, 2026
@leofang leofang added the P1 Medium priority - Should do label May 6, 2026
@rparolin rparolin enabled auto-merge (squash) May 6, 2026 15:12
cursor Bot pushed a commit that referenced this pull request May 12, 2026
Cherry-picked from PR #2029 (commit 18f5a02) to unblock pixi install.
Pixi's [package.target.<X>] only accepts platform identifiers; the
'python_version < "3.11"' selector caused parse failures.

Co-authored-by: Keith Kraus <kkraus14@users.noreply.github.com>
@rparolin rparolin merged commit 3b0f853 into NVIDIA:main May 12, 2026
193 of 199 checks passed
github-actions Bot pushed a commit that referenced this pull request May 13, 2026
Removed preview folders for the following PRs:
- PR #2029
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working cuda.core Everything related to the cuda.core module P1 Medium priority - Should do packaging Anything related to wheels or Conda packages

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants