<br><div class="gmail_quote">On Thu, May 29, 2008 at 9:12 AM, Georg Brandl <<a href="mailto:g.brandl@gmx.net">g.brandl@gmx.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Brett Cannon schrieb:<div class="Ih2E3d"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The issues related to PEP 3108 now total 14. With the beta<br>
(supposedly) in a week, I am hoping the last minor details can be<br>
pulled together or decisions made on what can be postponed and what<br>
should definitely be considered a release blocker.<br>
<br>
Issue 2847 - the aifc module still imports the cl module in 3.0.<br>
Problem is that the cl module is gone. =) So it seems silly to have<br>
the imports lying about. This can probably be changed to critical.<br>
</blockquote>
<br></div>
It shouldn't be a problem to rip everything cl-related out of aifc.<br>
The question is how useful aifc will be after that ...<div class="Ih2E3d"><br>
</div></blockquote></div><br>Has someone already used that module ? I took a look into it, but I'm a bit confused about the various compression types, case-sensitivity and compatibility issues [1]. Are Apple's "alaw" and SGI's "ALAW" really the same encoding ? Can we use the audioop module for ALAW, just like it's already done for ULAW ?<br>
<br>[1] <a href="http://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/AIFF/AIFF.html">http://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/AIFF/AIFF.html</a><br> <br>Quentin<br>