Maybe the best solution here is to simply add a "histogramkwargs"
argument that gets passed into nump.histogram - that way, the user can
also do things like have a weighted histogram if they so desire
(probably want to make sure no one passes in {'new':False}, though, as
that would screw everything
> what do you mean by "range" parameter. What should this parameter actually
> do ?
>
Actually just pass it along to numpy.histogram(). I guess it just ignores
all data outside the range.
Cheers,
Olle
-
Check out the new
Olle Engdegård wrote:
> Hi,
>
> Some more thoughts about hist():
>
> A "range" parameter should be added and used in histogram()
Hi Olle,
what do you mean by "range" parameter. What should this parameter
actually do ?
I just committed a patch to the trunk that adds the features as you
a
Hi,
Some more thoughts about hist():
A "range" parameter should be added and used in histogram()
A new histogram should get a new colour, just like plot() does
The "step" type should default to fill=False
Actually, personally I hardly ever use bar histograms at all, so if
step-mode (unfilled)
