Why use scipy.io.wave rather than stdlib wave?

[Russell-Jones]

Rather than
self.wav = scipy.io.wavfile.read(self.wavPath)
why not
self.wav = wave.open(self.wavPath, 'rb').readframes()
?

It's available in Python 2.6+ https://docs.python.org/2.6/library/wave.html
Is it to avoid type conversion complexities in 2.x?

[rudrathegreat]

See, both functions are the same thing. It is just that scipy's function can deal with larger wave-files in the same amount of time than it does for wave. Another reason is mentioned here -

python-acoustics/python-acoustics#220

But both functions have a lot of material on them so I am not really going to point that reason out.