Catch up to the latest histogram protocol. #219
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
|
@jpivarski I think it is fine. We are currently only debating whether an ordinary unweighted histogram should something .variances() or None, which does not really affect the interface, only how it should behave in the various cases. |
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.
The only change needed to catch up to
https://github.com/henryiii/uhi/blob/9fcfdc6158c686e58dfd31728b0aef4bd9572abe/uhi/typing/plottable.py
was to rename
interpretationaskindand make its output all upper-case.@henryiii @HDembinski, this should be ready for the non-release-candidate release, which I'll be starting now (first Awkward Array, then Uproot; should be about half an hour).