This repository was archived by the owner on Jun 3, 2025. It is now read-only.
Require torchvision<0.14 rather than torchvision<=0.13#1034
Merged
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
DeepSparse integration tests have been failing because we are restrictive on hotfix version for torchvision
We require torch==1.12.1 but restrict to torchvision==0.13 rather than allow 0.13.1
https://github.com/neuralmagic/deepsparse/actions/runs/5010952108/jobs/8981291327
My proposed fix is to change
torchvision>=0.3.0,<=0.13totorchvision>=0.3.0,<0.14Also, fix the SparseZoo change to use repo_name rather than model_id for the cache filepath