Henry Schreiner
Henry Schreiner
There are actually two distinct needs here. Using straw man terms for illustration, not intended to be the recommended names, just pointing out the two distinct uses: 1. `pick_one(axis_number, index)`...
You can disable mypy with `# type: ignore` if you need to. But "Adding things should be easy." - we need to be careful - the procedure is clear and...
> array((), dtype=object) It's slow and ugly, but fine for a first run. We could add easily Awkward support later.
> Why not drop Python 2 support now? 1.0 seems arbitrary. Randomly deciding that a feature patch should cause a major Python compatibility change is arbitrary. I have an outline...
> Any repetition in code is bad, we want to be DRY. This is not an absolute rule, just a guiding principle. Also, we really aren't talking about code duplication,...
We currently don't really support directly using awkward arrays. I'd like to, and it's planned, but calling to_numpy first is correct. And even if we support it, we'd basically be...
`.reset()` empties all the bins. It doesn't remove items from a growing axis (guessing that's what you mean?). Rather wishing we called it `.clear()` now. :)
This is clearly documented as "set counters to 0", so I think it's safe to close?
(The name comes from Boost.Histogram, otherwise I'd suggest renaming it to `.clear()`)
https://github.com/scikit-hep/boost-histogram#cheatsheet and https://boost-histogram.readthedocs.io/en/latest/usage/histogram.html#operations