-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
Should ExtensionArray.take accept scalar inputs? #22215
Comments
To be clear, I'm not sure that we should support it. Currently EA.take always returns an |
I'm Ok with |
Small note here: we seem to have explicitly added support for a scalar input in 0.18, see: http://pandas.pydata.org/pandas-docs/stable/whatsnew.html#whatsnew-0181-sparse (a section in the docs that is now failing). (re-opening as we at least have to fix the docs) |
Closes pandas-dev#22215 SparseArray.take not accepting scalars is already in 0.24.0.txt
Closes #22215 SparseArray.take not accepting scalars is already in 0.24.0.txt
Closes pandas-dev#22215 SparseArray.take not accepting scalars is already in 0.24.0.txt
Closes pandas-dev#22215 SparseArray.take not accepting scalars is already in 0.24.0.txt
Closes pandas-dev#22215 SparseArray.take not accepting scalars is already in 0.24.0.txt
Closes pandas-dev#22215 SparseArray.take not accepting scalars is already in 0.24.0.txt
Closes pandas-dev#22215 SparseArray.take not accepting scalars is already in 0.24.0.txt
ndarray.take accepts scalars, and returns a scalar. We should probably make that part of the interface, or document that we don't support it.
Categorical currently returns an invalid categorical:
take
The text was updated successfully, but these errors were encountered: