Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

2018-03-09 Thread Ralf Gommers
On Fri, Mar 9, 2018 at 12:00 AM, Nathaniel Smith wrote: > On Thu, Mar 8, 2018 at 10:26 PM, Ralf Gommers > wrote: > > > > > > On Thu, Mar 8, 2018 at 8:22 PM, Nathaniel Smith wrote: > >> > >> On Thu, Mar 8, 2018 at 7:06 AM, Marten van Kerkwijk > >> wrote: > >> > Hi Nathaniel, > >> > > >> > Overa

Re: [Numpy-discussion] new NEP: np.AbstractArray and np.asabstractarray

2018-03-09 Thread Nathaniel Smith
On Thu, Mar 8, 2018 at 5:51 PM, Juan Nunez-Iglesias wrote: >> Finally for the name, what about `asduckarray`? Thought perhaps that could >> be a source of confusion, and given the gradation of duck array like types. > > I suggest that the name should *not* use programmer lingo, so neither > "abstr

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

2018-03-09 Thread Nathaniel Smith
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] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

2018-03-09 Thread Nathaniel Smith
On Fri, Mar 9, 2018 at 11:51 AM, Stefan van der Walt wrote: > On Fri, 09 Mar 2018 17:00:43 +, Stephan Hoyer wrote: >> I'll note that we basically used GitHub for revising __array_ufunc__ NEP, >> and I think that worked out better for everyone involved. The discussion >> was a little too specia

Re: [Numpy-discussion] new NEP: np.AbstractArray and np.asabstractarray

2018-03-09 Thread Nathaniel Smith
On Thu, Mar 8, 2018 at 9:45 PM, Stephan Hoyer wrote: > On Thu, Mar 8, 2018 at 5:54 PM Juan Nunez-Iglesias > wrote: >> >> On Fri, Mar 9, 2018, at 5:56 AM, Stephan Hoyer wrote: >> >> Marten's case 1: works exactly like ndarray, but stores data differently: >> parallel arrays (e.g., dask.array), spa

[Numpy-discussion] NEP sprint: 21 and 22 March

2018-03-09 Thread Stefan van der Walt
Hi everyone, As you may have noticed, there's been quite a bit of movement recently around NumPy Enhancement Proposals---on setting specifications, building infrastructure, as well as writing new proposals. To further support this work, we will be hosting an informal NEP sprint at Berkeley on 21

Re: [Numpy-discussion] new NEP: np.AbstractArray and np.asabstractarray

2018-03-09 Thread Marten van Kerkwijk
We may be getting a bit distracted by the naming -- though I'll throw out `asarraymimic` as another non-programmer-lingo option that doesn't reuse `arraylike` and might describe what the duck array is attempting to do more closely. But more to the point: I think in essence, we're trying to create

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

2018-03-09 Thread Marten van Kerkwijk
Hi Nathaniel, astropy is an example of a project that does essentially all discussion of its "Astropy Proposals for Enhancement" on github. I actually like the numpy approach of sending anything to the mailing list that deserves community input (which includes NEP by their very nature). I don't th

Re: [Numpy-discussion] NumPy 1.14.2 release

2018-03-09 Thread Marten van Kerkwijk
Hi Chuck, Astropy tests indeed all pass again against master, without the work-arounds for 1.14.1. Thanks, of course also to Allan for the fix, Marten ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo

Re: [Numpy-discussion] new NEP: np.AbstractArray and np.asabstractarray

2018-03-09 Thread Ryan May
On Fri, Mar 9, 2018 at 12:21 AM, Hameer Abbasi wrote: > Not that I’m against different “levels” of ndarray granularity, but I just > don’t want it to introduce complexity for the end-user. For example, it > would be unreasonable to expect the end-user to check for all parts of the > interface tha

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

2018-03-09 Thread Stefan van der Walt
On Fri, 09 Mar 2018 17:00:43 +, Stephan Hoyer wrote: > I'll note that we basically used GitHub for revising __array_ufunc__ NEP, > and I think that worked out better for everyone involved. The discussion > was a little too specialized and high volume to be well handled on the > mailing list. A

Re: [Numpy-discussion] numpy.random.randn

2018-03-09 Thread Robert Kern
On Thu, Mar 8, 2018 at 12:44 PM, Marko Asplund wrote: > > On Wed, 7 Mar 2018 13:14:36, Robert Kern wrote: > > > > With NumPy I'm simply using the following random initilization code: > > > > > > np.random.randn(n_h, n_x) * 0.01 > > > > > > I'm trying to emulate the same behaviour in my Scala code

Re: [Numpy-discussion] new NEP: np.AbstractArray and np.asabstractarray

2018-03-09 Thread Ryan May
On Fri, Mar 9, 2018 at 2:29 AM, Nathaniel Smith wrote: > On Thu, Mar 8, 2018 at 7:06 AM, Marten van Kerkwijk > wrote: > > A larger comment: you state that you think `np.asanyarray` is a > > mistake since `np.matrix` and `np.ma.MaskedArray` would pass through > > and that those do not strictly mi

[Numpy-discussion] PR to add a function to calculate histogram edges without calculating the histogram

2018-03-09 Thread Kirit Thadaka
Hi! I've created a PR to add a function called "histogram_bin_edges" which will allow a user to calculate the bins used by the histogram for some data without requiring the entire histogram to be calculated. https://github.com/numpy/numpy/pull/10591#issuecomment-371863472 This function allows on

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

2018-03-09 Thread Stephan Hoyer
I'll note that we basically used GitHub for revising __array_ufunc__ NEP, and I think that worked out better for everyone involved. The discussion was a little too specialized and high volume to be well handled on the mailing list. On Fri, Mar 9, 2018 at 8:58 AM Stephan Hoyer wrote: > I also hav

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

2018-03-09 Thread Stephan Hoyer
I also have a slight preference for managing the discussion on GitHub, which is a bit more fully featured than email for long discussion (e.g., it supports code formatting and editing comments). But I'm really OK either way as long as discussion is kept in one place. We could still stipulate that

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

2018-03-09 Thread Charles R Harris
On Thu, Mar 8, 2018 at 11:26 PM, Ralf Gommers wrote: > > > On Thu, Mar 8, 2018 at 8:22 PM, Nathaniel Smith wrote: > >> On Thu, Mar 8, 2018 at 7:06 AM, Marten van Kerkwijk >> wrote: >> > Hi Nathaniel, >> > >> > Overall, hugely in favour! For detailed comments, it would be good to >> > have a li

Re: [Numpy-discussion] new NEP: np.AbstractArray and np.asabstractarray

2018-03-09 Thread Sebastian Berg
On Thu, 2018-03-08 at 18:56 +, Stephan Hoyer wrote: > Hi Nathaniel, > > Thanks for starting the discussion! > > Like Marten says, I think it would be useful to more clearly define > what it means to be an abstract array. ndarray has lots of > methods/properties that expose internal implementa

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

2018-03-09 Thread Julian Taylor
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  >

[Numpy-discussion] Endian dtype specifier without using character codes?

2018-03-09 Thread Matthew Brett
Hi, We (over at https://github.com/nipy/nibabel) often want to do stuff like this: ``` dtype_type = 'i' size = 8 endianness = '<' dtype = np.dtype('{}{}{}'.format(endianness, dtype_type, size)) ``` I see that """ Use of the character codes, however, is discouraged. """ https://docs.scipy.org/d

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

2018-03-09 Thread Carl Kleffner
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: np.AbstractArray and np.asabstractarray

2018-03-09 Thread Nathaniel Smith
On Thu, Mar 8, 2018 at 7:06 AM, Marten van Kerkwijk wrote: > A larger comment: you state that you think `np.asanyarray` is a > mistake since `np.matrix` and `np.ma.MaskedArray` would pass through > and that those do not strictly mimic `NDArray`. Here, I agree with > `matrix` (but since we're depre

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

2018-03-09 Thread Nathaniel Smith
On Thu, Mar 8, 2018 at 10:26 PM, Ralf Gommers wrote: > > > On Thu, Mar 8, 2018 at 8:22 PM, Nathaniel Smith wrote: >> >> On Thu, Mar 8, 2018 at 7:06 AM, Marten van Kerkwijk >> wrote: >> > Hi Nathaniel, >> > >> > Overall, hugely in favour! For detailed comments, it would be good to >> > have a li