Repository navigation
Conversation
This branch has not been deployed
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.
Description
DataArray.str.extract(..., dim=...)fails for NumPy variable-width string arrays because elements reaching the capture helper are Python strings without adtypeattribute. Use object arrays for the intermediate captures, then retain the existing cast to the input string dtype kind.The regression covers raw and compiled patterns for variable-width strings, Unicode and bytes, including optional groups and unmatched values. The entire string-accessor test module passed locally (265 tests), as did Ruff lint and formatting checks on the two Python files. Full project CI and the dependency/platform matrix remain outstanding.
Related to #11785; this addresses the extraction failure only.
Checklist
doc/whats-new.rst.