Fix support for importing from Lightning package #10417
Merged
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.
Fixes #9811
The fix proposed in #10404 was a step in the right direction by trying to import from the version installed by the user. However, as described in this comment, Lighting also installs a version of
pytorch_lightning. So it should be checked second, as it will be available whether the user originally installedlightningorpytorch_lightning.This is what the current PR does.
I tried implementing a test based on the example provided in #9811. However, I don't know how to dynamically (un)install packages (in this case
lightning) in the current environment. If you want a test for the issue, and know of a way to install packages at runtime, please point it to me and I'll try to adapt my existing local tests.EDIT: For reference, here are tables describing the compatibility between the Lightning package version installed and the import style:
Before this PR
pip install lightningpip install pytorch-lightningimport lightningimport pytorch_lightningAfter this PR
pip install lightningpip install pytorch-lightningimport lightningimport pytorch_lightning