-
-
Notifications
You must be signed in to change notification settings - Fork 18.3k
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
BUG: regression in error raised by idxmin/idxmax for extension dtypes #32749
Comments
sounds like a 2-liner to check for non-ndarray and raise the old exception? |
Maybe not necessarily, you might have EAs that can be converted to numerical ndarrays? |
Should values_for_argsort work for that? |
I suppose so? I suppose if argsort works on the values, also argmin/argmax should do the expected thing? |
I'd like to fix this by having In [52]: pd.array([1, 2, None], dtype="float64")._reduce("argmin", skipna=False) # PandasArray
Out[52]: <NA>
In [53]: pd.array([1, 2, None], dtype="Int64")._reduce("argmin", skipna=False)
Out[53]: -1 IMO, |
@TomAugspurger see also #33941, #33942 |
moved off 1.1.1 milestone (scheduled for this week) as no PRs to fix in the pipeline |
moved off 1.1.2 milestone (scheduled for this week) as no PRs to fix in the pipeline |
moved off 1.1.3 milestone (overdue) as no PRs to fix in the pipeline |
moved off 1.1.4 milestone (scheduled for release tomorrow) as no PRs to fix in the pipeline |
With pandas 1.0.1:
Now with master you get:
@jbrockmendel this is from no longer using
values_from_object
, but passing_values
to the nanops function, while this expects to always receive an ndarrayThe text was updated successfully, but these errors were encountered: