BUG: .describe() doesn't work for EAs #61707 #61910
Open
+30
−0
Conversation
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
|
Looks like this breaks some other tests |
simonjayhawkins
added
Bug
ExtensionArray
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes a bug where Series.describe() fails on certain
ExtensionArraydtypes such aspint[kg], due to attempting to cast the result toFloat64Dtype. This is because some of the produced statistics are not castable to float, which raises errors like DimensionalityError.We now avoid forcing a Float64Dtype return dtype when the EA’s scalar values cannot be safely cast. Instead:
If the EA produces outputs with mixed dtypes, the result is returned with
dtype=None.@jbrockmendel This is a new PR with the comments from 61760 addressed. Apologies for the duplication.