[WIP] Update pin for pytorch - #5123
Conversation
|
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/pytorch-cpu and so here I am doing that. |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
jakirkham
left a comment
There was a problem hiding this comment.
Let's hold off here. We are still working through some kinks with these packages in the feedstock: conda-forge/pytorch-cpu-feedstock#203
|
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/pytorch-cpu and so here I am doing that. |
|
Kinks have been worked out ^_^ |
|
Thanks Mark! 🥳 |
|
i feel like i'm getting clashes between torchvision and pytroch for cuda 11.2 and 11.8. is this a problem for other packages too? or just for pytorch related packages? |
|
Maybe we should start an issue somewhere with more details? Edit: Perhaps on the Edit 2: Also curious if this PR helped ( conda-forge/torchvision-feedstock#81 ) |
|
I think that the PR that helped was: conda-forge/torchvision-feedstock#80 and perhaps if I ever get around to finishing: |
This PR has been triggered in an effort to update the pin for pytorch. The current pinned version is 2.0, the latest available version is 2.1 and the max pin pattern is x.x. This migration will impact 33 feedstocks.
Checklist:
**Please note that if you close this PR we presume that the new pin has been rejected.
@conda-forge-admin please ping pytorch-cpu
This PR was generated by https://github.com/regro/cf-scripts/actions/runs/6778568921, please use this URL for debugging