New submission from Christophe Biocca: Basically, some (malformed or empty?) WAV strings result in the empty string being returned when calling readframes.
That string cannot be passed back to writeframes() without causing a crash, since it does not implement the buffer interface. ---------- components: Library (Lib) files: python_wave_error.py messages: 246575 nosy: Christophe Biocca priority: normal severity: normal status: open title: Certain inputs to wave.open() result in readframes returning a str instead of bytes type: behavior versions: Python 3.4 Added file: http://bugs.python.org/file39891/python_wave_error.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24608> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
