-
Notifications
You must be signed in to change notification settings - Fork 423
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
Fix backward compatability for older versions of lightning #182
Conversation
Codecov Report
@@ Coverage Diff @@
## master #182 +/- ##
==========================================
- Coverage 96.01% 87.70% -8.31%
==========================================
Files 180 180
Lines 5744 5750 +6
==========================================
- Hits 5515 5043 -472
- Misses 229 707 +478
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
can we also add an integration test for this as we have tested with PL 1.2 and they were all passing...
The problem seems to be cyclic import as the available func tries to import the package but in PL case it has TM as a dependency... |
@SkafteNicki seems that the integration fails... mind check it? |
Hello @SkafteNicki! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-04-20 09:08:09 UTC |
# lower lightning versions requires this implicitly to log metric objects correctly | ||
# in self.log | ||
if not _LIGHTNING_AVAILABLE or _LIGHTNING_GREATER_EQUAL_1_3: | ||
self._computed = None |
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.
isn't this backwards? shouldn't lightning be accounting for the torchmetrics version, not the other way around?
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.
since we cannot change earlier versions of lightning, we need to do the change in torchmetrics
Before submitting
What does this PR do?
Fixes #152
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃