Hi All,
I'm trying to update the .mailmap file on github and could use some help.
The current version seems common to both numpy and scipy, hence the
crosspost. Here is what I've got so far.
Alex Griffing ncsu.edu> alex ncsu.edu>
Alex Griffing ncsu.edu> argriffing ncsu.edu>
Alex Griffing nc
Chris Barker - NOAA Federal wrote:
> Which is part of the problem with C -- if two types happen to be the
> same, the compiler is perfectly happy.
That int and long int be the same is not more problematic than int and
signed int be the same.
Sturla
_
Hi All,
Just a heads up. If anything absolutely needed has been left out, please
make a noise.
Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
>> 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 is the C long that varies bet
