Fix test_melt with pyarrow strings active#10052
Conversation
jrbourbeau
left a comment
There was a problem hiding this comment.
Thanks @j-bennet
It's not totally clear to me whether this is a case where we should convert to string[pyarrow] or leave as object when combining mixed dtype columns (e.g. combining strings and floats). What's your thinking behind the current approach?
9461bd9 to
8105b19
Compare
This reverts commit 04164c5.
8105b19 to
d2d9805
Compare
For some reason, I had an impression that so the best fix seems to be to turn off |
dask/dataframe/utils.py
Outdated
| ( | ||
| a, | ||
| b, | ||
| ) = _maybe_convert_string(a, b) |
There was a problem hiding this comment.
I've not checked locally -- is pre-commit happy with this formatting? Not a big deal if we need what's current in this PR, but just thought I'd check
| ( | |
| a, | |
| b, | |
| ) = _maybe_convert_string(a, b) | |
| a, b = _maybe_convert_string(a, b) |
There was a problem hiding this comment.
This is what pre-commit did, for whatever reason! I didn't do that. :)
There was a problem hiding this comment.
Hrm, weird. When I make this change, pre-commit seems to be happy locally
There was a problem hiding this comment.
Yeah, it's happy now.
test_melttest_melt with pyarrow strings active
jrbourbeau
left a comment
There was a problem hiding this comment.
Thanks @j-bennet -- will merge after CI finishes
test_melt with pyarrow strings activetest_melt
|
Test failure is unrelated (upstream): |
test_melttest_melt with pyarrow strings active
Part of #10029.
Follow-up for #10000.
pre-commit run --all-files