Fix lightning imports #1179
Merged
Fix lightning imports #1179
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
datamodules
nilsleh
approved these changes
Mar 19, 2023
calebrob6
pushed a commit
that referenced
this pull request
Apr 10, 2023
* Fix lightning imports * Style fixes
yichiac
pushed a commit
to yichiac/torchgeo
that referenced
this pull request
Apr 29, 2023
* Fix lightning imports * Style fixes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #1178
Although some things (LightningModule, LightningDataModule, Trainer) get import aliases at the
lightninglevel, most other things (callbacks, loggers) don't. Even for things with import aliases, the docs still recommend importing them at thelightning.pytorchlevel. Let's stick with that everywhere for consistency.