-
Notifications
You must be signed in to change notification settings - Fork 915
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
[REVIEW] Fix find_common_dtype
and values
to handle complex dtypes
#12537
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## branch-23.04 #12537 +/- ##
===============================================
Coverage ? 85.66%
===============================================
Files ? 155
Lines ? 24822
Branches ? 0
===============================================
Hits ? 21263
Misses ? 3559
Partials ? 0 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
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.
On the whole, I am slightly negative about this approach to fixing the reported initial bugs. I think that upcasting to string columns isn't really an improvement and would rather see an error message that was appropriate.
Co-authored-by: Lawrence Mitchell <[email protected]>
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.
Looks good, except a question as to whether we should push the NotImplementedError
into find_common_type
.
/merge |
Description
Fixes: #12083, fixes #12115
This PR fixes
find_common_dtype
andvalues
APIs to handle complex dtypes by raising an error instead of casting them to strings.Checklist