On Jun 1, 2016 4:47 PM, "David Cournapeau" <courn...@gmail.com> wrote: > > > > On Tue, May 31, 2016 at 10:36 PM, Sturla Molden <sturla.mol...@gmail.com> wrote: >> >> Joseph Martinot-Lagarde <contreba...@gmail.com> wrote: >> >> > The problem with FFTW is that its license is more restrictive (GPL), and >> > because of this may not be suitable everywhere numpy.fft is. >> >> A lot of us use NumPy linked with MKL or Accelerate, both of which have >> some really nifty FFTs. And the license issue is hardly any worse than >> linking with them for BLAS and LAPACK, which we do anyway. We could extend >> numpy.fft to use MKL or Accelerate when they are available. > > > That's what we used to do in scipy, but it was a PITA to maintain. Contrary to blas/lapack, fft does not have a standard API, hence exposing a consistent API in python, including data layout involved quite a bit of work. > > It is better to expose those through 3rd party APIs.
Fwiw Intel's new python distribution thing has numpy patched to use mkl for fft, and they're interested in pushing the relevant changes upstream. I have no idea how maintainable their patches are, since I haven't seen them -- this is just from taking to people here at pycon. -n
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
