<p dir="auto">I've seen that v1.11 will be introducing aliases for different histogram binning optimization methods. I'm really looking forward to this feature, so thank you for implementing this!</p>
<p dir="auto">My question is how these methods will interact with the range parameter (this is not currently documented).</p>
<ul dir="auto">
<li>If the range is within (min, max), I imagine that the data sent to the binning method is restricted to this range.</li>
<li>If the range is extends beyond (min, max), I am not sure how this would be handled. Will methods that return a binwidth fill the entire range according to this binwidth? And will methods that return a number of bins be forced to expand their binwidth to cover the full range?</li>
</ul>
<p dir="auto">Travis CI has become too slow, simple PRs can take overnight to finish. Some of that is probably extra testing on the part of NumPy, OTOH, I look at the stats and active opensource builds are <a href="https://www.traviscistatus.com/" rel="nofollow">capped at 550 with a backlog of 10K</a> That doesn't seem healthy.</p>