Could we leave the fftpack module unchanged as a long-term legacy module, and create a new module, say scipy.fft? The interface of rfft in scipy.fftpack is really awkward to use.

I noticed that the dask FFT wrapper internally uses numpy 's FFT. Unless this is done to avoid a scipy dependency, I'd suggest switching to scipy.fft (not scipy.fftpack, which is now legacy) instead.

[153Armstrong] did a short post on how easy it is to generate waveforms using Python. We agree it is simple, but actually, it isn’t so much Python per se, it is some pretty cool libraries (SciPy ...

SciPy is an open-source scientific computing library for the Python programming language. Since its initial release in 2001, SciPy has become a de facto standard for leveraging scientific algorithms ...

Book Description Python has tremendous potential within the scientific computing domain. This updated edition of Scientific Computing with Python features new chapters on graphical user interfaces, ...