[issue24608] Certain inputs to wave.open() result in readframes returning a str instead of bytes

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. --

[issue24608] Certain inputs to wave.open() result in readframes returning a str instead of bytes

Roundup Robot added the comment: New changeset 9e035639516c by Serhiy Storchaka in branch '3.4': Issue #24608: chunk.Chunk.read() now always returns bytes, not str. https://hg.python.org/cpython/rev/9e035639516c New changeset 64b2d154a5db by Serhiy Storchaka in branch '3.5': Issue #24608:

[issue24608] Certain inputs to wave.open() result in readframes returning a str instead of bytes

Changes by Serhiy Storchaka storch...@gmail.com: -- assignee: - serhiy.storchaka nosy: +serhiy.storchaka stage: - needs patch versions: +Python 3.5, Python 3.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24608

[issue24608] Certain inputs to wave.open() result in readframes returning a str instead of bytes

Serhiy Storchaka added the comment: Thank you for your report Christophe. -- resolution: - fixed stage: needs patch - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24608