TYP: ravel: less awkward return types
#30224
Open
+4
−7
Conversation
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
b0cdce2 to
c72ee3a
Compare
rgommers
approved these changes
Nov 15, 2025
Member
rgommers
left a comment
There was a problem hiding this comment.
Thanks @jorenham. Seems fine to me. Given the discussion in gh-27032, pinging @Jacob-Stevens-Haas in case he has an opinion.
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.
this is a backwards-compatible change that makes the return types of
np.ravelfor nested sequences of python scalars less annoying, while still avoiding overlapping overloads (see #27032 (comment) for details).