-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
About pytorch 2.0 and pytorch-lightning #15894
Comments
Since 2.0 is completely backward compatible with 1.13, it will just work out of the box with Lightning. In fact, you can try it today from the nightlies. Installation instructions are here. In time, the team will add 2.0 to the CI testing suite to run all tests against it. Then there is the big new feature in 2.0 that allows you to compile the model with We can't give you a concrete ETA. So far, Lightning has always released a version shortly after the stable release of each PyTorch version with updated compatibility. We intend to follow that same pattern for 2.0. |
yes we will b testing it as son as they provide some public wheels, but until their official release (March 2023) we have about 4 months :) |
Just FYI @PoPdark, support for passing models produced by In order to try it out you'll need to have a recent PyTorch nightly installed alongside lightning. |
This went out with 1.8.4 https://github.com/Lightning-AI/lightning/releases/tag/1.8.4, closing the issue @PoPdark let me know if you have issues trying things out, remember you have to manually get the PyTorch nightlies to get |
Thanks! @lantiga Does it also work out of the box if |
For now we don't have a Trainer flag (say, So for the time being you need to do things just like the PyTorch docs say: model = MyModel()
model = torch.compile(model)
trainer = Trainer(...)
trainer.fit(model) Once we add a trainer flag you'll be able to enable compilation from the Lightning CLI. |
Yep, I think a |
Pytorch 2.0 will be released soon. I am wondering if you have the schedule to follow it? Thank you.
cc @Borda
The text was updated successfully, but these errors were encountered: