We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
torch 1.13 + transformers 4.39.0
torch.optim.LRScheduler was only exposed in torch 2:
torch.optim.LRScheduler
Previously it was called _LRScheduler in torch 1.
_LRScheduler
This recent PR included in 4.39.0 imports it and lead to a hard requirement on torch 2:
FYI @younesbelkada
This issue is captured by our CI where we have dependency on torch 1.
Suggest to check on version or API availability before use. Given it's only a visibility change, a transparent fallback/re-route would be ideal.
The text was updated successfully, but these errors were encountered:
This is a duplicate of #29847, I'll push something asap and do a patch release. FYI @LysandreJik and @amyeroberts
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
System Info
torch 1.13 + transformers 4.39.0
Description
torch.optim.LRScheduler
was only exposed in torch 2:Previously it was called
_LRScheduler
in torch 1.This recent PR included in 4.39.0 imports it and lead to a hard requirement on torch 2:
FYI @younesbelkada
This issue is captured by our CI where we have dependency on torch 1.
Expected behavior
Suggest to check on version or API availability before use.
Given it's only a visibility change, a transparent fallback/re-route would be ideal.
The text was updated successfully, but these errors were encountered: