classification
Title: aifc should use str instead of bytes (wave, sunau compatibility)
Type: behavior Stage:
Components: Library (Lib), Unicode Versions: Python 3.3, Python 3.4
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Arfrever, georg.brandl, r.david.murray, serhiy.storchaka, tjollans, vstinner
Priority: normal Keywords: patch

Created on 2010-06-07 18:56 by tjollans, last changed 2014-12-19 00:19 by Arfrever.

Files
File name Uploaded Description Edit
aifc_use_str.diff tjollans, 2010-06-07 18:55 patch: aifc: use str
aifc_str_doc.diff tjollans, 2010-06-07 20:53 library doc patch
Messages (3)
msg107274 - (view) Author: Thomas Jollans (tjollans) Date: 2010-06-07 18:55
aifc getcomptype() and setcomptype() use bytes while the corresponding methods in the sunau and wave modules use str (b'NONE', b'ULAW' vs 'NONE', 'ULAW'). This means that programmers wanting simple format-agnostic audio file output will have to special-case aifc. This was not necessary in Python 2.x, where all three modules used str (obviously). IMHO, there is no reason for this incompatibility.

The solution I propose is to change aifc to use unicode str for "information" strings and bytes for raw data only, like the other two modules. This is, the way I see it, the most sensible behaviour.

I'm attaching a patch that does just this: it changes aifc to use str for all (non-data) strings: comptype, compname, and markers. I've also changed the testcase accordingly.

The problem is, obviously, that this could break existing code. I doubt that it would break a lot of code since:
 - not that many people use aifc anyway (I think), and py3k is still
   young
 - py3k code that's out there now would most likely handle both
   scenarios anyway to account for the wave and sunau modules
 - setcomptype() would still accept bytes.

On the other hand, it would, as I said, simplify writing format-agnostic code. Special-casing any module wouldn't have been necessary with Python 2, why should Python 3 be any different?

There, I've made my case. Georg, I put you on the nosy list because of
  [svn r64023] Remove cl usage from aifc and use bytes throughout.
You, apparently, made the decision I'm arguing should be reverted, if indeed anyone consciously made it at all.

If this is applied, it would have to be properly documented, of course.
msg107278 - (view) Author: Thomas Jollans (tjollans) Date: 2010-06-07 20:53
tentative documentation patch uploaded
msg196869 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2013-09-03 20:37
I afraid we can't just change comptype to string. We can allow setcomptype() accept strings and convert them to bytes, but we can't change the type of getcomptype()'s result.
History
Date User Action Args
2014-12-19 00:19:36Arfreversetnosy: + Arfrever
2013-09-03 20:37:55serhiy.storchakasetmessages: + msg196869
2013-08-29 19:54:07serhiy.storchakasetnosy: + r.david.murray
2013-08-29 19:53:27serhiy.storchakasetnosy: + serhiy.storchaka

versions: + Python 3.4, - Python 3.1, Python 3.2
2010-06-07 20:53:09tjollanssetfiles: + aifc_str_doc.diff

messages: + msg107278
2010-06-07 19:48:29vstinnersetnosy: + vstinner
components: + Unicode
2010-06-07 18:56:04tjollanscreate