chore: Future proof release against uproot4 API changes #930
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.
Description
As @jpivarski mentioned that
uproot4
is going to have some API changes from theuproot
v3
releases, require that the version ofuproot
that is included in the releases untiluproot4
is released for broad use is using theuproot
v3
API.Once
uproot4
is released and stable this can get changed to usingto ensure that all future releases of
pyhf
get theuproot4
API.Checklist Before Requesting Reviewer
Before Merging
For the PR Assignees: