fix: strict AxesTuple constructor #680
Merged
Conversation
This file contains 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
henryiii
force-pushed
the
henryiii/fix/ATcons
branch
from
1ef6603
to
0be96cc
Compare
henryiii
changed the title
|
FYI, even though this is a minor fix, Hist was relying on the buggy behavior, so the next release needs to at least do a minor bump to avoid breaking Hist. 🤦. See scikit-hep/hist#368. |
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.
Closes #678.
Adding the check actually helped us, too -
.metadatawas incorrectlyreturning an
AxesTupleinstead of atuple, and there was an extra unneededAxesTupleconstruction.