Re: [stdlib-sig] standardizing the deprecation policy (and how noisy they are)
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? Thanks, S ___ stdlib-sig mailing list stdlib-sig@python.org http://mail.python.org/mailman/listinfo/stdlib-sig
Re: [stdlib-sig] standardizing the deprecation policy (and how noisy they are)
On Nov 9, 2009, at 1:11 PM, Guido van Rossum wrote: On Mon, Nov 9, 2009 at 10:05 AM, sstein...@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. Ok, thanks, S ___ stdlib-sig mailing list stdlib-sig@python.org http://mail.python.org/mailman/listinfo/stdlib-sig
Re: [stdlib-sig] futures - a new package for asynchronous execution
On Feb 23, 2010, at 5:00 PM, Guido van Rossum wrote: > On Tue, Feb 23, 2010 at 12:04 PM, Jeffrey Yasskin wrote: >> On Tue, Feb 23, 2010 at 3:31 AM, Brian Quinlan wrote: >>> >>> On Feb 22, 2010, at 2:37 PM, Jeffrey Yasskin wrote: >>> >>> Where's the current version of the PEP? >>> >>> >>> http://code.google.com/p/pythonfutures/source/browse/branches/feedback/PEP.txt > > Now in SVN as PEP 3148 - http://python.org/dev/peps/pep-3148/ I get a 404 on that URL. S ___ stdlib-sig mailing list stdlib-sig@python.org http://mail.python.org/mailman/listinfo/stdlib-sig
