-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST (string dtype): follow-up on GH-59329 fixing new xfails #59352
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
TST (string dtype): follow-up on GH-59329 fixing new xfails #59352
Conversation
elif isinstance(left, StringDtype): | ||
# TODO(infer_string) this special case could be avoided if we have | ||
# a more informative repr https://github.com/pandas-dev/pandas/issues/59342 | ||
left = f"StringDtype(storage={left.storage}, na_value={left.na_value})" |
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.
See #58451 (comment) for some discussion, but in short I am adding this for now because right now you can get test failures (like the ones that this PR is silencing with xfails) that have a very hard assert message like:
AssertionError: Attributes of DataFrame.iloc[:, 0] (column name="col1") are different
Attribute "dtype" are different
[left]: string[pyarrow]
[right]: string[pyarrow]
which is not very helpful ...
The reason for that is because I did not bake the pd.NA
vs np.nan
information in the string alias / representation.
We need to resolve that issue more in general (see the linked issue in the comment above), but short term this ensures that at least for developing and running tests, we can distinguish easily between the different dtypes.
The build (for future strings) is green again. I think it would be good to merge this rather quickly given it's fixing failures on main (will do in a few hours if no-one beats me to it). |
Thanks @jorisvandenbossche |
* TST (string dtype): follow-up on GH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
…pandas-dev#59352) * TST (string dtype): follow-up on pandas-devGH-59329 fixing new xfails * add missing strict
* TST (string dtype): follow-up on GH-59329 fixing new xfails * add missing strict
Follow-up on #59329, which caused some failures on main after being merged (see #59329 (comment))
xref #54792