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
__len__ for wrappers in dataset.py #1913
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1913 +/- ##
==========================================
- Coverage 88.46% 87.43% -1.03%
==========================================
Files 17 17
Lines 2306 2213 -93
==========================================
- Hits 2040 1935 -105
- Misses 266 278 +12
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.
Bedankt!
Could I ask you to add a couple of little tests for these as well? Search for e.g. test_asstr
to find relevant existing tests.
* __len__ function for AstypeWrapper | ||
* __len__ function for AsStrWrapper | ||
* __len__ function for FieldsWrapper |
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.
The class names aren't really obvious in the public API - I'd probably describe them as dset.astype()
etc.
Thank you for working on this @Mizzcoollizz ! The failure is still in
It looks like it is failing due to a miss-match between the name you put in Authors (your full name) and the name you told git and is being parsed out of the commit (just your first name). Could you please add a test for this? I know it seems trivial, but it will make sure we do not accidentally delete or refactor the functionality away in the future! Are there any other things would would want to forward from dset? Maybe |
Sorry you got simultaneous reviews! |
@Mizzcoollizz just checking if you're planning to come back to this? I think tests were the main thing both @tacaswell and I asked for in our reviews. 🙂 |
Thanks! Can you also add a test for h5py/h5py/tests/test_dataset.py Lines 1255 to 1275 in b578203
Also, unfortunately the author check is now seeing two different email addresses, and it wants to find both in |
I added a test for If you're happy for all of those details to be recorded in Github, the easiest thing is just add them all to |
Alternatively, I'm proposing we get rid of this authors check entirely (#1940). If the other maintainers agree with me, that will solve the issue. |
OK, we've got rid of the authors check that was causing these problems. As things stand, your two email addresses (gmail & kpn) will still be recorded in the commit history ( |
Hi! Thank you! Could you remove the kpn email? That email address doesn't exist and I'm not sure where it came from... |
No problem. |
…r and FieldsWrapper
Co-authored-by: Thomas Kluyver <takowl@gmail.com>
Thanks for your patience 🙂 |
No description provided.