Closed timmahrt closed 1 year ago
I wonder if it's worth the effort to split this up into a few separate PRs, given the sheer volume of changes. That might also help mitigate the build failures and reduce the burden of writing tests.
Could you also detail in the commit message what refactoring you did for audio.py
? For example, I'm not sure I understand the change from WavQueryObj
to QueryWav
.
I wonder if it's worth the effort to split this up into a few separate PRs, given the sheer volume of changes. That might also help mitigate the build failures and reduce the burden of writing tests.
I've basically rewritten the whole file. In hindsight I should have broken it into steps but I think its too late for that. I'll do my best to write comprehensive tests!
Could you also detail in the commit message what refactoring you did for audio.py? For example, I'm not sure I understand the change from WavQueryObj to QueryWav.
The names weren't great, so I renamed them. Maybe the new names aren't great either. If you have feedback, please share.
When the new version gets published, I'll have a changelog detailing all the removed/renamed/added methods.
I'm going to release a new version, so I'm trying to do as much cleaning as possible now, for things that I'm unsatisfied with.
I'll merge this into the release branch now. 🙏
audio.py suffers from a number of inconsistencies and bugs.
This PR aims to remove redundant methods and add documentation, and test coverage to audio.py