[stdlib-sig] standardizing the deprecation policy (and how noisy they are)

Guido van Rossum guido at python.org
Mon Nov 9 19:11:52 CET 2009

On Mon, Nov 9, 2009 at 10:05 AM, ssteinerX at gmail.com
<ssteinerx at gmail.com> wrote:
> On Nov 9, 2009, at 1:02 PM, Guido van Rossum wrote:
>> At Google we use a hacked-up version of pylint which seems infinitely
>> flexible in the checks you can specify. I assume that the public
>> version of pylint is just as capable -- someone just needs to write a
>> rule for it.
> Is that "hacked-up" version publicly available, or could it be?

I don't know and have no time to dive into this, but I suspect it
isn't of general interest, since AFAIK what we added is mostly rules
to enforce Google-specific coding standards.

--Guido van Rossum (python.org/~guido)

More information about the stdlib-sig mailing list