fix(python): convert object-dtyped NumPy str/bytes arrays to pl.String/pl.Binary instead of pl.Object #13712
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.
Closes #10710 (which was originally about the conversion to NumPy, but this PR addresses the underlying issue better).
Before:
After:
This will lead to errors on mixed-type object arrays where the first element is a string or bytes. I'd originally considered something like:
but that would be much slower since you'd have to iterate in Python over the entire array. More importantly, it would be inconsistent with the pandas-to-polars conversion, which also just checks the type of the first (non-null) element.