BUG: Ensure summed weights returned by np.average always are correct class (#30522)#30523
Merged
charris merged 1 commit intonumpy:maintenance/2.4.xfrom Dec 26, 2025
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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 #30522.
Over at astropy, it was noticed that if one passes in a
Quantityweight tonp.average, and asks for the summed weight to be returned, then the unit can be lost if the shapes of the weights and input array do not match (see astropy/astropy#19054). This is because of a missingsubok=Truein a final broadcast -- which this PR fixes (how I wish I had insisted more that that would be default forsubokwhen it was introduced...).