[Python-Dev] PEP 594: update 1
On Wed, May 22, 2019 at 1:23 PM Sean Wallitsch <
sean.wallitsch at dreamworks.com> wrote:
> My apologies for that oversight. My understanding is that many of the
> methods present in aifc depend heavily on audioop for reading and writing.
But are people using audioop directly? This shifts whether we still
publicly deprecate auidoop and make it an implementation detail of aifc
versus a free-standing module whose API we need to continue to support.
> On Wed, May 22, 2019 at 12:35 PM Nathaniel Smith <njs at pobox.com> wrote:
>> On Wed, May 22, 2019, 12:14 Sean Wallitsch <sean.wallitsch at dreamworks.com>
>>> Dear python-dev,
>>> I'm writing to provide some feedback on PEP-594, primarily the proposed
>>> deprecation and reason for the removal of the aifc and audioop libraries.
>>> The post production film industry continues to make heavy use of AIFFs,
>>> as completely uncompressed audio is preferred. Support for the consumer
>>> alternatives (ALAC, FLAC) is virtually non-existent, with no movement
>>> towards adoption of those formats. Even Apple's own professional editing
>>> tool Final Cut Pro does not support ALAC. Many of the applications also
>>> support WAV, but not all.
>>> Removal of this module from the standard library is complicated by the
>>> fact that a large number of film industry facilities have extremely limited
>>> internet access for security reasons. This does not make it impossible to
>>> get a library from pypi, but speaking to those devs has made me aware of
>>> what a painful process that is for them. They have benefited greatly from
>>> aifc's inclusion in the standard library.
>> That's really helpful data, thank you!
>> Is audioop also used? You mention both aifc and audioop at the beginning
>> and end of your message, but all the details in the middle focus on just
> Python-Dev mailing list
> Python-Dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...