-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
ENH: fix printing structured dtypes with a non-legacy dtype member #24758
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -51,6 +51,12 @@ def test_repr(self): | |
def test_dtype_name(self): | ||
assert SF(1.).name == "_ScaledFloatTestDType64" | ||
|
||
def test_sfloat_structured_dtype_printing(self): | ||
dt = np.dtype([("id", int), ("value", SF(0.5))]) | ||
# repr of structured dtypes need special handling because the | ||
# implementation bypasses the object repr | ||
assert "('value', '_ScaledFloatTestDType64')" in repr(dt) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A bit confusing, I woul;d have thout if the test above does EDIT: Ahh, nvm. I guess this and the above are actually very similar in what they use/define as "name". Hmmmm... |
||
|
||
@pytest.mark.parametrize("scaling", [1., -1., 2.]) | ||
def test_sfloat_from_float(self, scaling): | ||
a = np.array([1., 2., 3.]).astype(dtype=SF(scaling)) | ||
|
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.
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.
Yes, I am fine with this, although don't have
_legacy
now to do this?I am confused about this type of string, though, can't we use the
repr
?{byteorder}{TypeName}{itemsize}
doesn't need to be much of a reasonable repr?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.
I'm fine with just using the repr here and in the other path, I agree that the bitsize isn't particularly useful and if someone thinks it's worth including they can include it in the repr. Mind if I take care of that in a followup?
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.
Sure, I am fine with that, since its all in flux somewhat alpha stage anyway. Thanks @ngoldbaum lets just put it in.