Le 30 août 09 à 20:15, Frank Niessink a écrit : > 2009/8/30 Frank Niessink <[email protected]>: > > 2009/8/30 Jérôme Laheurte <[email protected]>: > >> > >> Personally, I prefer pychecker, it's not as anal as pylint when it > >> comes to perfectly valid but a bit too smart constructs. But it has > >> some issues with wx last time I checked, and pylint is much more > >> configurable. > > > > Yep, although I haven't been able to convince pylint not to check > the > > thirdparty package. But that may be a PyDev issue. > > BTW, I've been fixing pylint errors and warnings today in a few files > and already removed at least 3 instances of dead code and fixed at > least 2 (potential) bugs. Hopefully I can get the code in a state > where every error and warning is either removed or accepted (using # > pylint: disable-msg=<number>), so that when it gives you a warning or > error it's something to take seriously. >
Then I'll add a buildstep to the Buildbot so we don't miss anything :)
