[issue10198] wave module writes corrupt wav file for zero-length writeframes

Éric Araujo added the comment: Perfect, sorry for doubting you ;) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue10198] wave module writes corrupt wav file for zero-length writeframes

Georg Brandl added the comment: I always to the backports batched for these minor and docs fixes. -- ___ Python tracker ___ ___ Pytho

[issue10198] wave module writes corrupt wav file for zero-length writeframes

Éric Araujo added the comment: I asked that because I didn’t see the fix backported :) -- ___ Python tracker ___ ___ Python-bugs-list

[issue10198] wave module writes corrupt wav file for zero-length writeframes

Georg Brandl added the comment: I'm sorry, the actual revision is r85970. Why should it be irrelevant for other branches? -- ___ Python tracker ___ ___

[issue10198] wave module writes corrupt wav file for zero-length writeframes

Éric Araujo added the comment: That revision is actually an edit to re.rst. Is the patch irrelevant for other branches? -- nosy: +eric.araujo ___ Python tracker ___ ___

[issue10198] wave module writes corrupt wav file for zero-length writeframes

Georg Brandl added the comment: Thanks, fixed in r85914. -- nosy: +georg.brandl resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue10198] wave module writes corrupt wav file for zero-length writeframes

David Barnett added the comment: This patch against the python 2.6 version fixes the problem for me. -- keywords: +patch Added file: http://bugs.python.org/file19369/fix_double_header.patch ___ Python tracker

[issue10198] wave module writes corrupt wav file for zero-length writeframes

New submission from David Barnett : If the first call to writeframes happens to take an empty string as the data to write, then the next call to writeframes writes a 2nd header into the file, and forever after fails to patch the data length correctly. -- components: Library (Lib) messa