On Wed, Feb 18, 2009 at 3:06 AM, Nick Coghlan <ncoghlan at gmail.com> wrote: > Georg Brandl wrote: >> Benjamin Peterson schrieb: >>> Oh, does pylint support py3k now? >> >> I think you may have a point there, though I honestly don't know. > > I think it's a useful point in general - keeping something like pylint > or pychecker running correctly against the CPython trunk could be a > frustrating exercise on those occasions when we do change something that > the static checker then chokes on (mainly thinking syntax changes here - > they're obviously by far the minority of changes, but they do happen). > > Perhaps I'm being overly pessimistic, but my suspicion is that it would > end up being tantamount to bringing whichever tool we decided to use > into the standard library just to keep our own source tree passing cleanly. This prompts a wild idea -- perhaps the framework of 2to3 could be reused to create a new linter? -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4