> You may need to run the test code a few times to get the issue.
Okay, yeah, I can reproduce the #4007 issue now. Both with the 3.4 dmg from
python.org and the OSX wheel as well as 2.7 with numpy compiled from
source. I need to run the test [1] a couple times to get it.
But I think Sturla's obse
On Mon, Jun 9, 2014 at 5:08 AM, Robert McGibbon wrote:
> But I can't reproduce #4007 on my machine, so I'm not totally sure.
>
Are you using the current OSX wheel from pypi to install?
You may need to run the test code a few times to get the issue.
Cheers,
Matthew
_
But I can't reproduce #4007 on my machine, so I'm not totally sure.
-Robert
On Sun, Jun 8, 2014 at 9:07 PM, Robert McGibbon wrote:
> #4776 is definitely a separate issue. #4007 could be related similar f2c
> ABI issues, but I don't think so. The difference between the gfotran and
> g77/f2c AB
#4776 is definitely a separate issue. #4007 could be related similar f2c
ABI issues, but I don't think so. The difference between the gfotran and
g77/f2c ABIs, to my knowledge, is that (1) fortran REAL (single precision
floating point) return values are actually returned as a c double, not a c
flo
Hi,
On Mon, Jun 9, 2014 at 2:31 AM, Robert McGibbon wrote:
> Yeah, that's definitely not the right signature for sdot when linked against
> the Accelerate framework.
>
> But what's the purpose of those wrappers in _umath_linalg? The one for sdot,
> for example, doesn't appear to be used internall
Yeah, that's definitely not the right signature for sdot when linked
against the Accelerate framework.
But what's the purpose of those wrappers in _umath_linalg? The one for
sdot, for example, doesn't appear to be used internally, and it isn't
available from the python side. While scipy has all of
Julian Taylor wrote:
> probably a temporary commit that was never removed, it originates from 2008:
Should we get rid of it for NumPy 1.9?
Sturla
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/num
NumPy seems to define BLAS and LAPACK functions with gfortran ABI:
https://github.com/numpy/numpy/blob/master/numpy/linalg/umath_linalg.c.src#L289
extern float
FNAME(sdot)(int *n,
float *sx, int *incx,
float *sy, int *incy);
What happens on OS X where Accelerate Framework
On 09.06.2014 01:54, Sturla Molden wrote:
> Why does 64-bit MinGW require -O0 and -DDEBUG?
>
> https://github.com/numpy/numpy/blob/master/numpy/distutils/mingw32ccompiler.py#L120
>
> Is this a bug or intentional?
>
probably a temporary commit that was never removed, it originates from 2008:
co
Why does 64-bit MinGW require -O0 and -DDEBUG?
https://github.com/numpy/numpy/blob/master/numpy/distutils/mingw32ccompiler.py#L120
Is this a bug or intentional?
Sturla
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org
On Sun, Jun 8, 2014 at 2:34 PM, Julian Taylor wrote:
> Hello,
>
> I'm happy to announce the fist beta release of Numpy 1.9.0.
> 1.9.0 will be a new feature release supporting Python 2.6 - 2.7 and 3.2
> - 3.4.
> Due to low demand windows binaries for the beta are only available for
> Python 2.7, 3
Hello,
I'm happy to announce the fist beta release of Numpy 1.9.0.
1.9.0 will be a new feature release supporting Python 2.6 - 2.7 and 3.2
- 3.4.
Due to low demand windows binaries for the beta are only available for
Python 2.7, 3.3 and 3.4.
Please try it and report any issues to the numpy-discuss
12 matches
Mail list logo
