[Numpy-discussion] uarray update: API changes, overhead and comparison to __array_function__

2019-07-03 Thread Hameer Abbasi
Hello all, I just wrote a blog post on uarray and how it compares against NumPy’s __array_function__ protocol. Give it a read here: https://labs.quansight.org/blog/2019/07/uarray-update-api-changes-overhead-and-comparison-to-__array_function__/ Best Regards, Hameer Abbasi

Re: [Numpy-discussion] Problem with absolute value

2019-07-03 Thread Nicolas Rougier
Thanks for the quick explanation & answers. I was mostly puzzled by the absence of warning. In C you would get an overflow warning in such a case, no ? Nicolas > On 3 Jul 2019, at 20:01, Charles R Harris wrote: > > > > On Wed, Jul 3, 2019 at 11:39 AM Matthew Brett wrote: > Hi, > > On We

Re: [Numpy-discussion] Problem with absolute value

2019-07-03 Thread Charles R Harris
On Wed, Jul 3, 2019 at 11:39 AM Matthew Brett wrote: > Hi, > > On Wed, Jul 3, 2019 at 9:08 AM Charles R Harris > wrote: > > > > > > > > On Wed, Jul 3, 2019 at 9:08 AM Hameer Abbasi > wrote: > >> > >> Hi, > >> > >> It turns out you're running into a bit-error. In general, the two's > complement

Re: [Numpy-discussion] Problem with absolute value

2019-07-03 Thread Matthew Brett
Hi, On Wed, Jul 3, 2019 at 9:08 AM Charles R Harris wrote: > > > > On Wed, Jul 3, 2019 at 9:08 AM Hameer Abbasi > wrote: >> >> Hi, >> >> It turns out you're running into a bit-error. In general, the two's >> complement of -2 ** (n-1) with the bit-length being limited to n bits is >> itself...

Re: [Numpy-discussion] Problem with absolute value

2019-07-03 Thread Charles R Harris
On Wed, Jul 3, 2019 at 9:08 AM Hameer Abbasi wrote: > Hi, > > It turns out you're running into a bit-error. In general, the two's > complement of -2 ** (n-1) with the bit-length being limited to n bits is > itself... No way around that. And integers don't set hardware exceptions so > checking for

Re: [Numpy-discussion] Problem with absolute value

2019-07-03 Thread Hameer Abbasi
Hi, It turns out you're running into a bit-error. In general, the two's complement of -2 ** (n-1) with the bit-length being limited to n bits is itself... No way around that. And integers don't set hardware exceptions so checking for errors like these is hard as well. TL;DR: It's an error with

[Numpy-discussion] Problem with absolute value

2019-07-03 Thread Nicolas Rougier
Hi, I’m a bit surprised with the following code: >>> import numpy as np >>> np.seterr(all='warn') >>> Z = np.array([-128], dtype=np.byte) >>> print(np.abs(Z)) [-128] Obviously, it does not return the absolute value and I get no warning. Is it something expected ? (numpy 1.16.4, python 3.7.3)

Re: [Numpy-discussion] Top level release index page

2019-07-03 Thread Peter Cock
On Tue, Jul 2, 2019 at 11:19 PM Matti Picus wrote: > In PR 13886 I reworked the way the link to the release notes is > generated. The current page is > > > http://www.numpy.org/devdocs/release.html > > > and the new page is > > > > https://8001-908607-gh.circle-artifacts.com/0/home/circleci/repo