BUG: fix np.fromiter corruption when reusing a StringDType instance (#32012) - #32117
Merged
Conversation
…ce (numpy#32012) Co-authored-by: Gopu Yeshwanth Reddy <Gopu.Reddy@deshaw.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #32012.
PR summary
Fixes #32013
np.fromiteris buggy for StringDtype arrays. Specifically, when the dtype instance is already owned by someother array,it creates corrupted structures since it re-uses the input dtype instance to create the output array.
This PR fixes this issue to avoid using the input dtype descriptor to write the output.
Reproducer which this PR fixes:
AI Disclosure
I’ve used Claude Opus to shepherd this along.