Re: [Numpy-discussion] Integers to negative integer powers, time for a decision.

> Sounds good to me. I agree that we should prioritize within-numpy > consistency over consistency with Python. > I agree with that. Because of numpy consitetncy, the `**` operator should always return float. Right now the case is: >>> aa = np.arange(2, 10, dtype=int) array([2, 3, 4, 5, 6, 7, 8,

Re: [Numpy-discussion] Integers to negative integer powers, time for a decision.

but then that violates the numpy > principle that output dtypes should be determined entirely by input > dtypes, without peeking at the actual values. (And this rule is very > important for avoiding nasty surprises when you run your code on new > inputs.) > At division you get back an array of

Re: [Numpy-discussion] Integers to negative integer powers, time for a decision.

Sorry, I was not clear enough. I meant that the second option (always float) would be more coherent with Python3. On Oct 8, 2016 9:36 PM, "Charles R Harris" <charlesr.har...@gmail.com> wrote: On Sat, Oct 8, 2016 at 1:31 PM, Krisztián Horváth <raksi.ra...@gmail.com> wrote:

Re: [Numpy-discussion] Integers to negative integer powers, time for a decision.

Hello, I think it should be consistent with Python3. So, it should give back a float. Best regards, Krisztian On Sat, Oct 8, 2016 at 3:12 AM, Charles R Harris wrote: > Hi All, > > The time for NumPy 1.12.0 approaches and I like to have a final decision > on the