Re: [Python-Dev] PEP 594: update 1

2019-05-22 Thread Sean Wallitsch
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.

While development of the aifc and audioop libraries has slowed, this looks
consistent with mature projects and file formats that are not undergoing
constant change. Checking the bug tracker for aifc and audioop does not
paint a picture of these being broken or leaky modules requiring a lot of
dev time, and there are 2 community sourced pull requests in progress right
now.

The film industry may not make up a large chunk of python devs, but it is
python that makes tent pole films like Avengers possible. Without the
python digital asset management pipelines, films of that scale wouldn't be
possible.

Thank you for your time and consideration,

Sean Wallitsch
Lead Technical Director, DreamWorks Animation

On Wed, May 22, 2019 at 8:21 AM Brett Cannon  wrote:

>
>
> On Wed., May 22, 2019, 03:13 Antoine Pitrou,  wrote:
>
>> On Tue, 21 May 2019 17:44:16 -0700
>> Brett Cannon  wrote:
>> > >
>> > > So I should never have added those tests and then we wouldn't be
>> talking
>> > > about removing nntplib.
>> > >
>> >
>> > Not necessarily. I suspect it still would have been listed, you would
>> have
>> > objected, and someone may have looked at the tests to point out it was
>> only
>> > unit tests with no integration tests against a live service like e.g.
>> the
>> > pythontest.net-related tests and so it was already neglected.
>>
>> But that's moving the goalposts.
>
>
> I was just replying to your hypothetical with another hypothetical.
>
>   The PEP talks about "cruft,
>> unnecessary duplication of functionality, and dispensable features". Not
>> modules which have an insufficient test suite.
>>
>
> To me, untested code is a potential signal of cruft.
>
>
>> > It also doesn't help that no one is listed in the experts index for the
>> > module either.
>>
>> Right, but that's the case for many modules.
>>
>
> I never said I didn't view this PEP as conservative. 😉
>
> Anyway, my support of dropping nntplib is +0 so I personally support
> Christian if he wants to keep on the list but I'm also not that bothered if
> he wants to take it off the list.
>
> -Brett
>
>
>> Regards
>>
>> Antoine.
>>
>>
>> ___
>> Python-Dev mailing list
>> Python-Dev@python.org
>> https://mail.python.org/mailman/listinfo/python-dev
>> Unsubscribe:
>> https://mail.python.org/mailman/options/python-dev/brett%40python.org
>>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/sean.wallitsch%40dreamworks.com
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] PEP 594: update 1

2019-05-22 Thread Sean Wallitsch
My apologies for that oversight. My understanding is that many of the
methods present in aifc depend heavily on audioop for reading and writing.

On Wed, May 22, 2019 at 12:35 PM Nathaniel Smith  wrote:

> On Wed, May 22, 2019, 12:14 Sean Wallitsch 
> wrote:
>
>> 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
> aifc.
>
> -n
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] OpenGrok upgraded and is now self serve

2020-02-12 Thread Sean Wallitsch
OpenGrok  has moved to the DreamWorks Cloud!

It's on a much beefier VM this time around, which will hopefully alleviate
the crashing and downtime that plagued the old instance. In addition,
Opengrok now re-indexes every *60 *minutes instead of once a day. It will
also auto-pull github changes down during that time.

Finally, you can add your own github repositories or folios to be indexed
by following "Adding Files to OpenGrok"

on the mydw  page.
It's as simple as ssh'ing in to grokdev, then either git cloning or
symlinking the repository you want indexed.

Good luck, and happy searching.

-Sean
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/QEPMMB3HPUPM6DZFPA2EDZX5M3UN3QX2/
Code of Conduct: http://python.org/psf/codeofconduct/


[Python-Dev] Re: OpenGrok upgraded and is now self serve

2020-02-12 Thread Sean Wallitsch
Please ignore this email, it was accidentally sent to this group.

My most sincere apologies.

On Wed, Feb 12, 2020 at 5:05 PM Sean Wallitsch <
sean.wallit...@dreamworks.com> wrote:

> OpenGrok <http://opengrok/> has moved to the DreamWorks Cloud!
>
> It's on a much beefier VM this time around, which will hopefully alleviate
> the crashing and downtime that plagued the old instance. In addition,
> Opengrok now re-indexes every *60 *minutes instead of once a day. It will
> also auto-pull github changes down during that time.
>
> Finally, you can add your own github repositories or folios to be indexed
> by following "Adding Files to OpenGrok"
> <http://mydw.dreamworks.net/display/TD/Opengrok#Opengrok-AddingFilestoOpenGrok>
> on the mydw <http://mydw.dreamworks.net/display/TD/Opengrok> page.
> It's as simple as ssh'ing in to grokdev, then either git cloning or
> symlinking the repository you want indexed.
>
> Good luck, and happy searching.
>
> -Sean
>
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/FSDQPQSHLAOFPNROGT63VK65OEI6FJO4/
Code of Conduct: http://python.org/psf/codeofconduct/