Re: [Numpy-discussion] Proposal: Deprecate np.int, np.float, etc.?

2015-07-31 Thread Sturla Molden
Chris Barker - NOAA Federal wrote: > Turns out I was passing in numpy arrays that I had typed as "np.int". > It worked OK two years ago when I was testing only on 32 bit pythons, > but today I got a bunch of failed tests on 64 bit OS-X -- a np.int is > now a C long! It has always been C long. It

Re: [Numpy-discussion] Proposal: Deprecate np.int, np.float, etc.?

2015-07-31 Thread Nathaniel Smith
On Jul 24, 2015 08:55, "Julian Taylor" wrote: > > On 07/23/2015 04:29 AM, Nathaniel Smith wrote: > > Hi all, > > > > So one of the things exposed in the numpy namespace are objects called > >np.int > >np.float > >np.bool > > etc. > > > > These are commonly used -- in fact, just yesterd

Re: [Numpy-discussion] Proposal: Deprecate np.int, np.float, etc.?

2015-07-31 Thread Chris Barker - NOAA Federal
So one more bit of anecdotal evidence: I just today revived some Cython code I wrote a couple years ago and haven't tested since. It wraps a C library that uses a lot of "int" typed values. Turns out I was passing in numpy arrays that I had typed as "np.int". It worked OK two years ago when I wa

Re: [Numpy-discussion] Proposal: Deprecate np.int, np.float, etc.?

2015-07-31 Thread Jason Newton
On Fri, Jul 31, 2015 at 5:19 PM, Nick Papior wrote: > -- > > Kind regards Nick Papior > On 31 Jul 2015 17:53, "Chris Barker" wrote: > > > > On Thu, Jul 30, 2015 at 11:24 PM, Jason Newton wrote: > >> > >> This really needs changing though. scientific researchers don't catch > this subtlety and

Re: [Numpy-discussion] Proposal: Deprecate np.int, np.float, etc.?

2015-07-31 Thread Nick Papior
-- Kind regards Nick Papior On 31 Jul 2015 17:53, "Chris Barker" wrote: > > On Thu, Jul 30, 2015 at 11:24 PM, Jason Newton wrote: >> >> This really needs changing though. scientific researchers don't catch this subtlety and expect it to be just like the c and matlab types they know a little abo

Re: [Numpy-discussion] Proposal: Deprecate np.int, np.float, etc.?

2015-07-31 Thread Sturla Molden
Chris Barker wrote: > What about Fortan -- I've been out of that loop for ages -- does > semi-modern Fortran use well defined integer types? Modern Fortran is completely sane. INTEGER without kind number (Fortran 77) is the fastest integer on the CPU. On AMD64 that is 32 bit, because it is desi

Re: [Numpy-discussion] Proposal: Deprecate np.int, np.float, etc.?

2015-07-31 Thread Chris Barker
On Thu, Jul 30, 2015 at 11:24 PM, Jason Newton wrote: > This really needs changing though. scientific researchers don't catch > this subtlety and expect it to be just like the c and matlab types they > know a little about. > well, C types are a %&$ nightmare as well! In fact, one of the biggest

Re: [Numpy-discussion] Proposal: Deprecate np.int, np.float, etc.?

2015-07-31 Thread Julian Taylor
On 31.07.2015 08:24, Jason Newton wrote: > Been using numpy in it's various forms since like 2005. burned on int, > int_ just today with boost.python / ndarray conversions and a number of > times before that. intc being C's int!? Didn't even know it existed > till today. This isn't the first tim