Open almostimplemented opened 2 years ago
Hi there,
Did we use torchvision
somewhere in the repo? Could you point me to that?
Thanks!
-Yuan
Hi there,
Did we use
torchvision
somewhere in the repo? Could you point me to that?Thanks!
-Yuan
Hi Yuan,
If you follow the call stack you can see the dependency arises from import timm
from ast_models.py
Thanks! I just checked, it seems we use torchvision==0.10.0+cu102
>>> torch.__version__
'1.8.1+cu102'
>>> torchaudio.__version__
'0.8.1'
>>> torchvision.__version__
'0.10.0+cu102'
It's weird that no one has complained about this issue. I assume the order you install these three packages also matters.
I suspect it is more to do with when the user installed the dependencies rather than the order -- I think the breaking change came only in the 0.12.0 release:
https://github.com/pytorch/vision/releases/tag/v0.12.0
Without pinning the version in the requirements file, pip will get the latest. So anyone who set up before that point would have avoided the issue -- or perhaps anyone who installed into a Python environment with torchvision
already installed / cached at a lower version.
Would you like the version changed to 0.10.0
?
Yes, but I will need to test it before changing it.
Thanks again for pointing this out.
A regular check on the traffic of this repo shows that many people are searching this issue - which means this bug affects many people. Follow your suggestion I have pinned torchvision
to 0.10.0
. I don't have time to make a test but hope that would makes things better.
If anyone still experience this bug, please leave a message in this thread and I will take another look.
-Yuan
Following setup instructions at present will lead to an error on the model import. Specifically,
torchvision
needs to be pinned to a version. Otherwise,pip
may install (e.g.) 0.12.0, which expectstorch==1.11.0
when it importstorch.ao
.