Re: [Numpy-discussion] Moving NumPy's PRNG Forward

2018-01-26 Thread Robert Kern
On Sat, Jan 27, 2018 at 1:14 AM, Kevin Sheppard wrote: > > I am a firm believer that the current situation is not sustainable. There are a lot of improvements that can practically be incorporated. While many of these are performance related, there are also improvements in accuracy over some ranges

Re: [Numpy-discussion] Setting custom dtypes and 1.14

2018-01-26 Thread josef . pktd
On Fri, Jan 26, 2018 at 5:48 PM, Chris Barker wrote: > On Fri, Jan 26, 2018 at 2:35 PM, Allan Haldane > wrote: > >> As I remember, numpy has some fairly convoluted code for array creation >> which tries to make sense of various nested lists/tuples/ndarray >> combinations. It makes a difference f

Re: [Numpy-discussion] Setting custom dtypes and 1.14

2018-01-26 Thread Chris Barker
On Fri, Jan 26, 2018 at 2:35 PM, Allan Haldane wrote: > As I remember, numpy has some fairly convoluted code for array creation > which tries to make sense of various nested lists/tuples/ndarray > combinations. It makes a difference for structured arrays and object > arrays. I don't remember the

Re: [Numpy-discussion] Setting custom dtypes and 1.14

2018-01-26 Thread Allan Haldane
On 01/26/2018 03:38 PM, Chris Barker wrote: > I was hoping it would dig down to the inner structures looking for a > match to the dtype, rather than looking at the type of the top level. Oh > well. > > So yeah, not sure where you would go from tuple to list -- probably at > the bottom level, but t

Re: [Numpy-discussion] Setting custom dtypes and 1.14

2018-01-26 Thread Eric Wieser
arr.names should have been arr.dtype.names in that pack_last_axis function Eric ​ On Fri, 26 Jan 2018 at 12:45 Chris Barker wrote: > On Fri, Jan 26, 2018 at 10:48 AM, Allan Haldane > wrote: > >> > What do folks think about a totuple() method — even before this I’ve >> > wanted that. But in t

Re: [Numpy-discussion] Setting custom dtypes and 1.14

2018-01-26 Thread Chris Barker
On Fri, Jan 26, 2018 at 10:48 AM, Allan Haldane wrote: > > What do folks think about a totuple() method — even before this I’ve > > wanted that. But in this case, it seems particularly useful. > > Two thoughts: > > 1. `totuple` makes most sense for 2d arrays. But what should it do for > 1d or 3

Re: [Numpy-discussion] Setting custom dtypes and 1.14

2018-01-26 Thread Eric Wieser
Apologies, it seems that I skipped to the end of @ahaldane's remark - we're on the same page. On Fri, 26 Jan 2018 at 11:17 Eric Wieser wrote: > Why is the list of tuples a useful thing to have in the first place? If > the goal is to convert an array into a structured array, you can do that > far

Re: [Numpy-discussion] Setting custom dtypes and 1.14

2018-01-26 Thread Eric Wieser
Why is the list of tuples a useful thing to have in the first place? If the goal is to convert an array into a structured array, you can do that far more efficiently with: def make_tup_dtype(arr): """ Attempt to make a type capable of viewing the last axis of an array, even if it is non-co

Re: [Numpy-discussion] Setting custom dtypes and 1.14

2018-01-26 Thread Allan Haldane
On 01/25/2018 08:53 PM, Chris Barker - NOAA Federal wrote: >> On Jan 25, 2018, at 4:06 PM, Allan Haldane wrote: > >>> 1) This is a known change with good reason? > >> . The >> change occurred because the old assignment behavior was dangerous, and >> was not doing what you thought. > > OK, that’

Re: [Numpy-discussion] Moving NumPy's PRNG Forward

2018-01-26 Thread Kevin Sheppard
I am a firm believer that the current situation is not sustainable. There are a lot of improvements that can practically be incorporated. While many of these are performance related, there are also improvements in accuracy over some ranges of parameters that cannot be incorporated. I also think t