-
Notifications
You must be signed in to change notification settings - Fork 129
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
check for is_string_dtype and unsupported mixed type #335
Conversation
@jdawang @ak-gupta @gladysteh99 friendly ping :) |
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.
Other than this minor comment, the rest looks good to me!
datacompy/core.py
Outdated
if pd.api.types.infer_dtype(col_1).startswith("mixed") or pd.api.types.infer_dtype( | ||
col_1 | ||
).startswith("mixed"): |
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.
is this supposed to be pd.api.types.infer_dtype(col_2).startswith("mixed")
instead for the second clause?
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.
ahh yes. typo!
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.
LGTM pending resolution of @gladysteh99's comment
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.
LGTM!
Fixes #327
This is a breaking change in that we would no longer support mixed column types. As one can imagine, that mixed types can get super complex and cumbersome to manage.
The proposal here is to NOT support mixed types moving forward with
v0.14.0