Re: [Numpy-discussion] (2012) Accessing LAPACK and BLAS from the numpy C API

2012-03-10 Thread sole
Hi Sturla, Quoting Sturla Molden : > Den 10.03.2012 22:56, skrev Sturla Molden: >> >> I am not sure why NumPy uses f2c'd routines instead of a dependency >> on BLAS and LAPACK like SciPy. > > Actually, np.dot does depend on the CBLAS interface to BLAS (_dotblas.c). > > But the lapack methods in

Re: [Numpy-discussion] (2012) Accessing LAPACK and BLAS from the numpy C API

2012-03-10 Thread Pauli Virtanen
10.03.2012 23:19, Sturla Molden kirjoitti: [clip] > If the intention is to avoid Fortran dependency in NumPy, I am not sure > why this is better than a dependency on CBLAS and LAPACKE. The CBLAS parts aren't compiled if the library is not available --- in that case Numpy just falls back to a total

Re: [Numpy-discussion] (2012) Accessing LAPACK and BLAS from the numpy C API

2012-03-10 Thread Sturla Molden
Den 10.03.2012 22:56, skrev Sturla Molden: I am not sure why NumPy uses f2c'd routines instead of a dependency on BLAS and LAPACK like SciPy. Actually, np.dot does depend on the CBLAS interface to BLAS (_dotblas.c). But the lapack methods in lapack_lite seems to use f2c'd code. I am not sur

Re: [Numpy-discussion] (2012) Accessing LAPACK and BLAS from the numpy C API

2012-03-10 Thread Sturla Molden
Den 07.03.2012 21:02, skrev "V. Armando Solé": I had already used the information Robert Kern provided on the 2009 thread and obtained the PyCObject as: from scipy.linalg.blas import fblas dgemm = fblas.dgemm._cpointer sgemm = fblas.sgemm._cpointer but I did not find a way to obtain those po

Re: [Numpy-discussion] (2012) Accessing LAPACK and BLAS from the numpy C API

2012-03-10 Thread Sturla Molden
Den 07.03.2012 21:02, skrev "V. Armando Solé": I had already used the information Robert Kern provided on the 2009 thread and obtained the PyCObject as: from scipy.linalg.blas import fblas dgemm = fblas.dgemm._cpointer sgemm = fblas.sgemm._cpointer but I did not find a way to obtain those po

Re: [Numpy-discussion] (2012) Accessing LAPACK and BLAS from the numpy C API

2012-03-07 Thread V. Armando Solé
On 06/03/2012 20:57, Sturla Molden wrote: On 05.03.2012 14:26, "V. Armando Solé" wrote: In 2009 there was a thread in this mailing list concerning the access to BLAS from C extension modules. If I have properly understood the thread: http://mail.scipy.org/pipermail/numpy-discussion/2009-Novem

Re: [Numpy-discussion] (2012) Accessing LAPACK and BLAS from the numpy C API

2012-03-06 Thread Sturla Molden
On 06.03.2012 21:33, David Cournapeau wrote: > Of course it does make his life easier. This way he does not have to > distribute his own BLAS/LAPACK/etc... > > Please stop presenting as truth things which are at best highly > opiniated. You already made such statements many times, and it is not >

Re: [Numpy-discussion] (2012) Accessing LAPACK and BLAS from the numpy C API

2012-03-06 Thread David Cournapeau
On Tue, Mar 6, 2012 at 2:57 PM, Sturla Molden wrote: > On 05.03.2012 14:26, "V. Armando Solé" wrote: > >> In 2009 there was a thread in this mailing list concerning the access to >> BLAS from C extension modules. >> >> If I have properly understood the thread: >> >> http://mail.scipy.org/pipermail

Re: [Numpy-discussion] (2012) Accessing LAPACK and BLAS from the numpy C API

2012-03-06 Thread Sturla Molden
On 05.03.2012 14:26, "V. Armando Solé" wrote: > In 2009 there was a thread in this mailing list concerning the access to > BLAS from C extension modules. > > If I have properly understood the thread: > > http://mail.scipy.org/pipermail/numpy-discussion/2009-November/046567.html > > the answer by t

[Numpy-discussion] (2012) Accessing LAPACK and BLAS from the numpy C API

2012-03-05 Thread V. Armando Solé
Hello, In 2009 there was a thread in this mailing list concerning the access to BLAS from C extension modules. If I have properly understood the thread: http://mail.scipy.org/pipermail/numpy-discussion/2009-November/046567.html the answer by then was that those functions were not exposed (only