-
-
Notifications
You must be signed in to change notification settings - Fork 11.1k
BUG: Any dtype should call square
on arr ** 2
#29392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
seberg
merged 5 commits into
numpy:main
from
MaanasArora:bug/structured-arr-fast-square
Jul 22, 2025
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
d8eeb76
BUG: update fast_scalar_power to handle special-case squaring for any…
MaanasArora 097b04a
BUG: fix missing declaration
MaanasArora 79a91a1
TST: add test to ensure `arr**2` calls square for structured dtypes
MaanasArora e014ffe
STY: remove whitespace
MaanasArora ddaef11
BUG: replace new variable `is_square` with direct op comparison in `f…
MaanasArora File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, yeah this seems right/safe to me. I am not sure I see why
**2
confuses a custom__array_ufunc__
, but I don't think this is an issue (and probably restores old behavior). (If we had a bigger reason to keep it as is, I would be tempted to ask downstream to fix it there.)Curious, does
**0.5
always end up withsqrt()
?(Maybe the nicer solution for at least
**2
would actually be to make the objectsquare
implementation use**2
internally then this special case wouldn't even be needed. But no priority so if, let's do that as a follow-up.)