On Tue, 03 Jan 2017, Stephan Hoyer wrote:
> >> testing on stable debian box with elderly numpy, where it does behave
> >> sensibly:
> >> $> python -c "import numpy; print('numpy version: ', numpy.__version__);
> >> a=2; b=-2; print(pow(a,b)); print(pow(numpy.array(a), b))"
> >> ('numpy version:
On Tue, Jan 3, 2017 at 3:05 PM, Nathaniel Smith wrote:
> It's possible we should back off to just issuing a deprecation warning in
> 1.12?
>
> On Jan 3, 2017 1:47 PM, "Yaroslav Halchenko" wrote:
>
>> hm... testing on current master (first result is from python's pow)
>>
>> $> python -c "import n
It's possible we should back off to just issuing a deprecation warning in
1.12?
On Jan 3, 2017 1:47 PM, "Yaroslav Halchenko" wrote:
>
> On Tue, 03 Jan 2017, Stephan Hoyer wrote:
>
> >On Tue, Jan 3, 2017 at 9:00 AM, Yaroslav Halchenko <
> li...@onerussian.com>
> >wrote:
>
> > Sorry f
On Tue, 03 Jan 2017, Stephan Hoyer wrote:
>On Tue, Jan 3, 2017 at 9:00 AM, Yaroslav Halchenko
>wrote:
> Sorry for coming too late to the discussion and after PR "addressing"
> the issue by issuing an error was merged [1].A I got burnt by new
> behavior while trying to bu
On Tue, Jan 3, 2017 at 9:00 AM, Yaroslav Halchenko
wrote:
> Sorry for coming too late to the discussion and after PR "addressing"
> the issue by issuing an error was merged [1]. I got burnt by new
> behavior while trying to build fresh pandas release on Debian (we are
> freezing for release way
On Tue, 11 Oct 2016, Peter Creasey wrote:
> >> I agree with Sebastian and Nathaniel. I don't think we can deviating from
> >> the existing behavior (int ** int -> int) without breaking lots of existing
> >> code, and if we did, yes, we would need a new integer power function.
> >> I think it's be
