mirror of
https://github.com/astral-sh/uv.git
synced 2025-07-07 21:35:00 +00:00
Replace cuda124 with cuda128 (#14168)
## Summary <!-- What's the purpose of the change? What does it do, and why? --> Replace wrong `cuda124` version to the correct `cuda128` version in torch docs ## Test Plan <!-- How was it tested? -->
This commit is contained in:
parent
c710246d76
commit
563e9495ba
1 changed files with 3 additions and 3 deletions
|
@ -355,11 +355,11 @@ explicit = true
|
|||
|
||||
In some cases, you may want to use CPU-only builds in some cases, but CUDA-enabled builds in others,
|
||||
with the choice toggled by a user-provided extra (e.g., `uv sync --extra cpu` vs.
|
||||
`uv sync --extra cu124`).
|
||||
`uv sync --extra cu128`).
|
||||
|
||||
With `tool.uv.sources`, you can use extra markers to specify the desired index for each enabled
|
||||
extra. For example, the following configuration would use PyTorch's CPU-only for
|
||||
`uv sync --extra cpu` and CUDA-enabled builds for `uv sync --extra cu124`:
|
||||
`uv sync --extra cpu` and CUDA-enabled builds for `uv sync --extra cu128`:
|
||||
|
||||
```toml
|
||||
[project]
|
||||
|
@ -410,7 +410,7 @@ explicit = true
|
|||
!!! note
|
||||
|
||||
Since GPU-accelerated builds aren't available on macOS, the above configuration will fail to install
|
||||
on macOS when the `cu124` extra is enabled.
|
||||
on macOS when the `cu128` extra is enabled.
|
||||
|
||||
## The `uv pip` interface
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue