➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author harveyormston
Recipients harveyormston, jcea, mark.dickinson, seebk
Date 2013-02-15.17:22:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1360948922.45.0.462499247619.issue16525@psf.upfronthosting.co.za>
In-reply-to
Content 
I see that this issue applies to Python 3.4. Nevertheless, I am now using the submitted patch (http://bugs.python.org/file28122/wave_float_issue16525.patch) with Python 2.7.

I find that the patched module fails when calling getwavformat(), becuase the _wavformat attribute is not set.

I attach wave_read_issue16525.patch, which properly sets the _wavformat attribute and allows getwavformat() to succeed.

Apologies if I have not followed the proper process here. I found this patch a while ago while looking for a solution to the limitations in the standard wave module and, upon using the patch, identified this potential issue which I have attampted to fix. I thought it would be best to share that fix.
History
Date User Action Args
2013-02-15 17:22:02harveyormstonsetrecipients: + harveyormston, jcea, mark.dickinson, seebk
2013-02-15 17:22:02harveyormstonsetmessageid: <1360948922.45.0.462499247619.issue16525@psf.upfronthosting.co.za>
2013-02-15 17:22:02harveyormstonlinkissue16525 messages
2013-02-15 17:22:02harveyormstoncreate