Toby Thurston added the comment:
I think it's probably better as a no-op. Currently in my patch I just put
return data
You could do
return data[::-1]
to reverse the sample, so that it came out as big endian, but if you leave it
as a no-op then the data is returned in the native format for Intel Mac OS,
which is the whole point of the "sowt" encoding. Either way, the user can
easily reverse the data in a `unpack` format if they want to, but in my own
testing it seemed easier and simpler just to leave it in the native format.
Then basically "it just works".
The patch as I've proposed it works fine on my MacOS boxes, but I have only
tested it with AIFF-C files from one source.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30077>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
