Re: [Numpy-discussion] New NEP: merging multiarray and umath

On Mon, Mar 12, 2018 at 1:25 PM, Nathaniel Smith wrote: > On Mar 12, 2018 12:02, "Charles R Harris" > wrote: > > > If we accept this NEP, I'd like to get it done soon, preferably and the > next few months, so that it is finished before we drop Python 2.7 support. > That will make maintenance of

Re: [Numpy-discussion] New NEP: merging multiarray and umath

On Mar 12, 2018 12:02, "Charles R Harris" wrote: If we accept this NEP, I'd like to get it done soon, preferably and the next few months, so that it is finished before we drop Python 2.7 support. That will make maintenance of the NumPy long term support release through 2019 easier. The reason

Re: [Numpy-discussion] New NEP: merging multiarray and umath

On Thu, Mar 8, 2018 at 1:25 AM, Nathaniel Smith wrote: > Hi all, > > Well, this is something that we've discussed for a while and I think > generally has consensus already, but I figured I'd write it down > anyway to make sure. > > There's a rendered version here: > https://github.com/njsmith/num

Re: [Numpy-discussion] New NEP: merging multiarray and umath

Hi Nathanial, I looked through the revised text at https://github.com/numpy/numpy/pull/10704 and think it covers things well; any improvements on the organisation I can think of would seem to start with doing the merge anyway (e.g., I quite like Eric Wieser's suggested base ndarray class; the addi

Re: [Numpy-discussion] New NEP: merging multiarray and umath

> Am 09.03.2018 um 02:06 schrieb Nathaniel Smith : > > On Thu, Mar 8, 2018 at 1:52 AM, Gregor Thalhammer > mailto:gregor.thalham...@gmail.com>> wrote: >> >> Hi, >> >> long time ago I wrote a wrapper to to use optimised and parallelized math >> functions from Intels vector math library >> geggo

Re: [Numpy-discussion] New NEP: merging multiarray and umath

On Fri, Mar 9, 2018 at 3:33 AM, Julian Taylor wrote: > As the functions of the different libraries have vastly different > accuracies you want to be able to exchange numeric ops at runtime or at > least during load time (like our cblas) and not limit yourself one > compile time defined set of func

Re: [Numpy-discussion] New NEP: merging multiarray and umath

On 08.03.2018 17:20, Charles R Harris wrote: > > > On Thu, Mar 8, 2018 at 2:52 AM, Gregor Thalhammer > mailto:gregor.thalham...@gmail.com>> wrote: > > > Hi, > > long time ago I wrote a wrapper to to use optimised and parallelized > math functions from Intels vector math library  >

Re: [Numpy-discussion] New NEP: merging multiarray and umath

2018-03-09 2:06 GMT+01:00 Nathaniel Smith : > On Thu, Mar 8, 2018 at 1:52 AM, Gregor Thalhammer > wrote: > > > > Hi, > > > > long time ago I wrote a wrapper to to use optimised and parallelized math > > functions from Intels vector math library > > geggo/uvml: Provide vectorized math function (MK

Re: [Numpy-discussion] New NEP: merging multiarray and umath

On Thu, Mar 8, 2018 at 1:52 AM, Gregor Thalhammer wrote: > > Hi, > > long time ago I wrote a wrapper to to use optimised and parallelized math > functions from Intels vector math library > geggo/uvml: Provide vectorized math function (MKL) for numpy > > I found it useful to inject (some of) the fa

Re: [Numpy-discussion] New NEP: merging multiarray and umath

I think part of the problem is that ufuncs actually have two parts: a generic interface, which turns all its arguments into ndarray (or calls `__array_ufunc__`) and an ndarray-specific implementation of the given function (partially, just the iterator, partially the inner loop). The latter could lo

Re: [Numpy-discussion] New NEP: merging multiarray and umath

On Thu, Mar 8, 2018 at 9:20 AM, Charles R Harris wrote: > > > On Thu, Mar 8, 2018 at 2:52 AM, Gregor Thalhammer < > gregor.thalham...@gmail.com> wrote: > >> >> Hi, >> >> long time ago I wrote a wrapper to to use optimised and parallelized math >> functions from Intels vector math library >> geggo

Re: [Numpy-discussion] New NEP: merging multiarray and umath

On Thu, Mar 8, 2018 at 4:52 AM, Gregor Thalhammer wrote: > > Hi, > > long time ago I wrote a wrapper to to use optimised and parallelized math > functions from Intels vector math library > geggo/uvml: Provide vectorized math function (MKL) for numpy > > I found it useful to inject (some of) the fa

Re: [Numpy-discussion] New NEP: merging multiarray and umath

On Thu, Mar 8, 2018 at 2:52 AM, Gregor Thalhammer < gregor.thalham...@gmail.com> wrote: > > Hi, > > long time ago I wrote a wrapper to to use optimised and parallelized math > functions from Intels vector math library > geggo/uvml: Provide vectorized math function (MKL) for numpy >

Re: [Numpy-discussion] New NEP: merging multiarray and umath

Hi, long time ago I wrote a wrapper to to use optimised and parallelized math functions from Intels vector math library geggo/uvml: Provide vectorized math function (MKL) for numpy I found it useful to inject (some of) the fast methods into numpy via np.set_nu

Re: [Numpy-discussion] New NEP: merging multiarray and umath

On Thu, Mar 8, 2018 at 12:47 AM, Eric Wieser wrote: > This means that ndarray needs to know about ufuncs – so instead of a clean > layering, we have a circular dependency. > > Perhaps we should split ndarray into a base_ndarray class with no arithmetic > support (add, sum, etc), and then provide a

Re: [Numpy-discussion] New NEP: merging multiarray and umath

This means that ndarray needs to know about ufuncs – so instead of a clean layering, we have a circular dependency. Perhaps we should split ndarray into a base_ndarray class with no arithmetic support (*add*, sum, etc), and then provide an ndarray subclass from umath instead (either the separate e