MAINT: gracefully shuffle memoryviews#18327
Merged
charris merged 2 commits intonumpy:maintenance/1.20.xfrom Feb 4, 2021
Merged
MAINT: gracefully shuffle memoryviews#18327charris merged 2 commits intonumpy:maintenance/1.20.xfrom
charris merged 2 commits intonumpy:maintenance/1.20.xfrom
Conversation
* allow graceful shuffling of memoryviews, with same behavior as arrays, instead of producing a warning on `memoryview` shuffle
* based on reviewer feedback, instead of explicitly supporting `memoryview` shuffling via `asarray()`, support the shuffling implicitly by using `Sequence` instead of `MutableSequence`
This was referenced Mar 8, 2021
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
2 participants
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 #18282.
Fixes gh-18273
same behavior as arrays, instead of producing
a warning on
memoryviewshuffleThere's certainly some contention that me doing this downstream was sub-optimal anyway, but I don't think there's any claim that it should be disallowed/considered a bug to shuffle a memoryview.
I was originally going to special case 1-D C-contiguous memoryviews, but the discussion in the matching issue seems to suggest that just using
asarray()without fancy special casing might be the way to go?