Skip to content

docs: make more use of the rich platform syntax - #6711

Open
ruben-arts wants to merge 3 commits into
prefix-dev:mainfrom
ruben-arts:docs/rich-platform-updates
Open

docs: make more use of the rich platform syntax#6711
ruben-arts wants to merge 3 commits into
prefix-dev:mainfrom
ruben-arts:docs/rich-platform-updates

Conversation

@ruben-arts

@ruben-arts ruben-arts commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Description

Improving documentation related to rich platforms and gpu environments

Improving this was triggered by #6625

AI Disclosure

  • This PR contains AI-generated content.
    • I have tested any AI-generated content in my PR.
    • I take responsibility for any AI-generated content in my PR.

Tools:Claude

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • [na] I have added sufficient tests to cover my changes.
  • [na] I have verified that changes that would impact the JSON schema have been made in schema/model.py.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the PyTorch + GPU documentation examples to emphasize Pixi’s “rich platform” and [target]-based configuration, replacing multi-environment examples with per-platform targeting.

Changes:

  • Switched the PyTorch CPU/GPU examples from feature/environment splitting to named rich platforms with [target] selectors (including wildcard selectors for *-cpu / *-cuda).
  • Updated the PyTorch guide to explain platform selection, naming pitfalls, and using pixi run --platform.
  • Revised the manifest reference’s per-feature constraints example.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
docs/source_files/pyproject_tomls/pytorch-pypi-envs.toml Updates PyPI PyTorch example to use named rich platforms and wildcard [tool.pixi.target] selectors.
docs/source_files/pyproject_tomls/pytorch-conda-forge-envs.toml Updates conda-forge PyTorch example to use named rich platforms and platform-specific targets.
docs/source_files/pixi_tomls/pytorch-pypi-envs.toml Mirrors the PyPI example changes for pixi.toml format using [target."*-cpu/*-cuda"].
docs/source_files/pixi_tomls/pytorch-conda-forge-envs.toml Mirrors the conda-forge example changes for pixi.toml format using named targets.
docs/reference/pixi_manifest.md Updates per-feature constraints example (needs adjustment to avoid an unrealistic Python version constraint).
docs/python/pytorch.md Updates narrative and commands to reflect per-platform targeting and platform selection behavior.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/reference/pixi_manifest.md

@Hofer-Julian Hofer-Julian left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks, added a few comments

Comment thread docs/python/pytorch.md Outdated
Comment thread docs/python/pytorch.md Outdated
in the `legacy-gpu` environment it sees `cuda = "<12"`.
If both features were active in the same environment the solver would receive both
constraints and would need to find a version that satisfies all of them.
The above example will produce an environment with `mkdocs` and `python` installed, but the solver will make sure that the Python version is at least 3.14.0 and that `click` is not version 8.1.7.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Let's make the example an actual toml where we at least test the syntax in CI

ruben-arts and others added 2 commits July 30, 2026 11:01
Co-authored-by: Hofer-Julian <30049909+Hofer-Julian@users.noreply.github.com>
Co-authored-by: Hofer-Julian <30049909+Hofer-Julian@users.noreply.github.com>
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.

3 participants