-
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
Support returning python scalars in DP #1935
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1935 +/- ##
======================================
+ Coverage 89% 90% +1%
======================================
Files 79 79
Lines 7302 7214 -88
======================================
- Hits 6514 6496 -18
+ Misses 788 718 -70 |
@nsarang good addition. Can you write a test for this? |
Could you then also update the docs, since you mention there are wrong informations on the return type? |
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.
as mentioned by Will and Adrian, pls
- add tests
- update docs
@nsarang how is it going here? 🐰 |
@Borda Sorry I've been busy lately. I'll finish it today 🙂 |
Hello @nsarang! Thanks for updating this PR.
Comment last updated at 2020-08-06 12:23:29 UTC |
@Borda This warning is supposed to be silenced in ignored_warnings.py but It seems the text doesn't match 🤔 I could add this line to the |
This pull request is now in conflict... :( |
This pull request is now in conflict... :( |
@nsarang mind check the tests, pls |
mind checking the failing test? @nsarang |
@Borda @williamFalcon |
@nateraw mind have look? 🐰 |
Before submitting
What does this PR do?
Fixes #1861 and #1904.
I'm not sure if this fix is the right approach. In the docs it's mentioned that
training_step
must returnTensor
(even for theprogress_bar
dict). But with this PR it'll also work with scalars. Were there other reasons (besides the issues above) to force users to stick with tensors?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 🙃