-
Notifications
You must be signed in to change notification settings - Fork 763
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
Move from pytorch_lightning
to lightning
#3013
Conversation
@@ -2,7 +2,7 @@ | |||
|
|||
```{toctree} | |||
:maxdepth: 1 | |||
howto_pytorch_lightning | |||
howto_lightning.pytorch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This slipped in I guess?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One change to revert in the docs I believe, otherwise looks good, thank you @shchur!
pytorch_lightning
to lightning
* [torch] Return a model even if callback has no best model path (#2952) * Move from `pytorch_lightning` to `lightning` (#3013) --------- Co-authored-by: Kashif Rasul <[email protected]> Co-authored-by: Oleksandr Shchur <[email protected]>
Hi, maybe I'm doing something else wrong, but this new import syntax seems to not work with |
Thanks @caseytomlin, we have released v0.13.7 that uses the old import style and therefore is compatible with the correct version ranges. We will update the version ranges in v0.14.0, where the the new import style will be introduced. |
Description of changes:
load_from_checkpoint
introduced bypytorch_lightning==2.1.0
.lightning
instead ofpytorch_lightning
lightning.pytorch
instead ofpytorch_lightning
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup