Automatically infer the PyTorch index via --torch-backend=auto
#12070
+1,284
−117
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
charliermarsh
force-pushed
the
charlie/ltt
branch
from
7742e65 to
232dc9b
Compare
charliermarsh
force-pushed
the
charlie/ltt
branch
2 times, most recently
from
30de9fd to
9d06dfb
Compare
charliermarsh
force-pushed
the
charlie/ltt
branch
from
9d06dfb to
3e85795
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This is a prototype that I'm considering shipping under
--preview, based onlight-the-torch.light-the-torchpatches pip to pull PyTorch packages from the PyTorch indexes automatically. And, in particular,light-the-torchwill query the installed CUDA drivers to determine which indexes are compatible with your system.This PR implements equivalent behavior under
--torch-backend auto, though you can also set--torch-backend cpu, etc. for convenience. When enabled, the registry client will fetch from the appropriate PyTorch index when it sees a package from the PyTorch ecosystem (and ignore any other configured indexes, unless the package is explicitly pinned to a different index).Right now, this is only implemented in the
uv pipCLI, since it doesn't quite fit into the lockfile APIs given that it relies on feature detection on the currently-running machine.