Wed, 04 Nov 2009 21:15:48 -0700, Charles R Harris wrote:
[clip]
>  ATLAS is a moving target and who knows what will cause trouble in the
>  future. On top of that, it is trying to get the best performance and
>  that is likely to mean code somewhere that likes aligned data. I've now
>  read the ticket and I think you are right to just use the new alignment
>  option added to f2py. I don't think you should wait too long on the
>  ATLAS folks.

Ah yes, using the f2py functionality is a correct fix, too, now that I 
remember it again :)

I agree that it's best to just go ahead with the workaround already, and 
if the Atlas/LAPACK people find a fix, we can take the workarounds out.

(Note that the eig-headaches.diff patch contains

    for a in arrays:
+       break
        a = numpy.asarray(a)

Maybe it's best to remove the whole loop?)

-- 
Pauli Virtanen

_______________________________________________
Scipy-dev mailing list
Scipy-dev@[...].org
http://mail.scipy.org/mailman/listinfo/scipy-dev