So, raise a ValueError when it used to return (mostly) correct results? For
some reason, I don't think people would appreciate that.
Ben Root
On Jan 13, 2015 5:59 PM, "Chris Barker" wrote:
> On Tue, Jan 13, 2015 at 7:23 AM, Benjamin Root wrote:
>
>> Oh, wow. I never noticed that before. Yeah, i
On Tue, Jan 13, 2015 at 7:23 AM, Benjamin Root wrote:
> Oh, wow. I never noticed that before. Yeah, if I state that retstep=True,
> then I am coding my handling to expect two values to be returned, not 1. I
> think it should be nan, but I could also agree with zero. It should
> definitely remain
On Mon, Jan 12, 2015 at 7:23 PM, Alexander Belopolsky
wrote:
>
> On Mon, Jan 12, 2015 at 8:48 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
> > I've often fantasized getting rid of the long type altogether ;) So it
> isn't exactly intended, but there is a reason...
>
>
> It is also
On Tue, Jan 13, 2015 at 7:23 AM, Benjamin Root wrote:
> Oh, wow. I never noticed that before. Yeah, if I state that retstep=True,
> then I am coding my handling to expect two values to be returned, not 1. I
> think it should be nan, but I could also agree with zero. It should
> definitely remain
Oh, wow. I never noticed that before. Yeah, if I state that retstep=True,
then I am coding my handling to expect two values to be returned, not 1. I
think it should be nan, but I could also agree with zero. It should
definitely remain a float value, though.
Cheers!
Ben Root
On Tue, Jan 13, 2015 a
While working on something else, I realized that linspace is not handling
requests for returning the sampling spacing consistently:
>>> np.linspace(0, 1, 3, retstep=True)
(array([ 0. , 0.5, 1. ]), 0.5)
>>> np.linspace(0, 1, 1, retstep=True)
array([ 0.])
>>> np.linspace(0, 1, 0, retstep=True)
arr
