-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: Avoid casting Int to object in Categorical.from_codes #31794
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
Changes from 4 commits
416a869
4bd7588
6c2edda
916998f
270199a
75e25d6
acbadaa
6ec804e
c5508dc
63b7c1c
e9edcfb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -644,7 +644,11 @@ def from_codes(cls, codes, categories=None, ordered=None, dtype=None): | |
) | ||
raise ValueError(msg) | ||
|
||
codes = np.asarray(codes) # #21767 | ||
if is_extension_array_dtype(codes) and is_integer_dtype(codes): | ||
# Avoid the implicit conversion of Int to object | ||
codes = codes.to_numpy(dtype=np.int64, na_value=np.nan) | ||
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. Codes shouldn't contain missing values (and the |
||
else: | ||
codes = np.asarray(codes) # #21767 | ||
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. you don't need to add the issue number in code generally, unless you add a full expl (so here just remove i) |
||
if len(codes) and not is_integer_dtype(codes): | ||
raise ValueError("codes need to be array-like integers") | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -560,6 +560,15 @@ def test_from_codes_neither(self): | |
with pytest.raises(ValueError, match=msg): | ||
Categorical.from_codes([0, 1]) | ||
|
||
def test_from_codes_with_nullable_int(self): | ||
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. can you also test with a NaN in the codes and Int64 (should raise) 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. Done. The error message that ends up getting raised is maybe not the best: 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. Yes, I think we should probably catch the error to raise a better one (because the error message now would be really confusing for users) |
||
codes = pd.array([0, 1], dtype="Int64") | ||
categories = ["a", "b"] | ||
|
||
result = Categorical.from_codes(codes, categories=categories) | ||
expected = Categorical.from_codes(codes.astype(int), categories=categories) | ||
dsaxton marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
tm.assert_categorical_equal(result, expected) | ||
|
||
@pytest.mark.parametrize("dtype", [None, "category"]) | ||
def test_from_inferred_categories(self, dtype): | ||
cats = ["a", "b"] | ||
|
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.
Hmm does this universally work if we just call
to_numpy
? I suppose could copy where undesired but maybe better than if...else branchingThere 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.
Yeah the if / else isn't too pretty but I think we have to worry if
codes
is a numpy array already or possibly a bare list. Ideally it'd be nice to just dopd.array(codes)
instead ofnp.asarray(codes)
, but it looks likemin
andmax
haven't been implemented yet for IntegerArray so we get an error soon after.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.
In principle we could do a
pd.array(codes).to_numpy("int64")
But a problem with that is that it will convert an already integer array of potentially lower bitsize than int64
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.
Has numpy a concept of "any integer dtype"?
Because then we could also simply do
codes = np.asarray(codes, dtype="any int")
Another option could be this (to avoid converting an already int ndarray to int64)::
which seems simpler as what you have now
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 think we want it to raise if codes is something like
[0.0, 1.0, 2.0]
but this would make it a valid inputThere 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.
Ah, yes indeed...
(we should probably try to gather some of those situations we run into handling array-like input including nullable dtypes, to see if we can extract some useful helpers for those cases)