-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Locked version of timm
dependency
#620
Comments
The reason is that API tends to change, especially in such quick-developing libraries as timm! In one day you can appear with not working code because of that, I prefer to fix the version, but you can always update it after installing. |
Would it be possible to lock it based on semver to something like I've noticed that this isn't exactly the first issue to request support for modern versions of timm...
Given that one of the most popular feature requests in this library is upgrading the version of timm, I think it's safe to say that the current solution is problematic. |
I have updated timm version, but a new version, unfortunately, breaks the code |
I will fix and update it later, there are some changes, not seeing a quick fix for it |
Yeah, looks like TorchGeo doesn't work with segmentation_models_pytorch 0.3 either: microsoft/torchgeo#692. Hoping we can figure out how to support both 0.2 and 0.3 so we don't have to pin to a specific version. |
On my side I add to change |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Is there a reason to depend on specific version of PyTorch Image Models
timm==0.4.12
instead of using something like>=0.4.12
as a version specifier?The context for the question is this issue.
The text was updated successfully, but these errors were encountered: