Skip to content

docs(pyproject): clarify uv is required for installation#441

Open
x4v13r64 wants to merge 1 commit into
intel:mainfrom
x4v13r64:docs/note-uv-required
Open

docs(pyproject): clarify uv is required for installation#441
x4v13r64 wants to merge 1 commit into
intel:mainfrom
x4v13r64:docs/note-uv-required

Conversation

@x4v13r64

@x4v13r64 x4v13r64 commented Jun 5, 2026

Copy link
Copy Markdown

The four samples that pin packages to the PyTorch XPU wheel index (Finetune_Image_Captioning, Genre-driven-storytelling, LLM/PyTorch, AI-Upscaling-With-NPU) rely on [tool.uv.sources] + [[tool.uv.index]] to resolve torch, torchvision, torchaudio, and pytorch-triton-xpu from https://download.pytorch.org/whl/xpu. Vanilla pip does not parse these blocks, so a developer who runs pip install -e . instead of uv sync will not find the XPU wheels (they are not on PyPI).

The READMEs already document uv as the install tool for three of the four directories, but the pyproject is what someone reads when they are already inside the codebase. Adding a one-paragraph note above the [tool.uv.sources] block makes the requirement local to the file, so anyone who reaches for pip first sees why it will not work.

Pure-comment change: no behavior, no dependency, no formatting touched.

Adds a comment above the [tool.uv.sources] block in the four pyproject.toml
files that pin packages to the PyTorch XPU wheel index. The note explains
that uv must be used to install these samples because vanilla pip does not
parse [tool.uv.sources] / [[tool.uv.index]] and will not find the XPU
wheels on PyPI.

The READMEs already say to use uv, but the pyproject is what a developer
reads when they're already poking at the codebase, so making the
requirement local to the file helps anyone who tries pip first.
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