-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add pytorch integration guide. #2711
docs: add pytorch integration guide. #2711
Conversation
Co-authored-by: Tim de Jager <[email protected]>
Co-authored-by: Tim de Jager <[email protected]>
Co-authored-by: Tim de Jager <[email protected]>
@ruben-arts: thanks for this work, I think it really clarifies compatibilities and offers concrete solutions to users of pixi! Excellent job! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small suggestion, up to you @ruben-arts if you want to apply it.
The testing looks good for now.
@ruben-arts and I agree that we want to move the "extra_slow" tests to their own workflow as a follow-up
Co-authored-by: Hofer-Julian <[email protected]>
Initial write-up of the use of PyTorch with pixi.
Thanks to @anjos and @hadim for helping me with my previous attempt, this version is based on #2123
This adds 3 different ways of installing PyTorch to the documentation under
Features
.Testing
We've added a test setup to test these examples, so all TOML information is part of actual TOML files and "snippeted" into the documentation. These TOML files are run in CI by installing them on all platforms that the examples are supported on. E.g.
conda-forge
doesn't support windows yet.Because this test blown up the windows' runner, I took the liberty to also split the tests like we talked about. I'm not proud of doing it in this PR, but I rather don't merge failing CI