Hi there !
I'm very pleased to announce the new 0.8 release of PyLint. I've promised this release for a long time now, and finally got the time to do it :D. This release includes a lot of bug fixes and enhancements. Notice that a major change in this release is a new dependancy to the astng package which has been extracted from logilab-common. This package is downloadable from http://www.logilab.org/projects/astng.
What's new ? ------------ * check names imported from a module exists in the module (E0611), patch contributed by Amaury Forgeot d'Arc
* print a warning (W0212) for methods that could be a function (implements #9100)
* new --defining-attr-methods option on classes checker
* new --acquired-members option on the classes checker, used when --zope=yes to avoid false positive on acquired attributes (listed using this new option) (close #8616)
* generate one E0602 for each use of an undefined variable (previously, only one for the first use but not for the following) (implements #1000) * make profile option saveable
* fix Windows .bat file, patch contributed by Amaury Forgeot d'Arc * fix one more false positive for E0601 (access before definition) with for loop such as "for i in range(10): print i" (test func_noerror_defined_and_used_on_same_line)
* fix false positive for E0201 (undefined member) when accessing to __name__ on a class object
* fix astng checkers traversal order
* fix bug in format checker when parsing a file from a platform using different new line characters (close #9239) * fix encoding detection regexp
* fix --rcfile handling (support for --rcfile=file, close #9590)
What is pylint ? ----------------
Pylint is a python tool that checks if a module satisfy a coding standard. Pylint can be seen as another pychecker since nearly all tests you can do with pychecker can also be done with Pylint. But Pylint offers some more features, like checking line-code's length, checking if variable names are well-formed according to your coding standard, or checking if declared interfaces are truly implemented, and much more (see http://www.logilab.org/projects/pylint/ for the complete check list). The big advantage with Pylint is that it is highly configurable, customizable, and you can easily write a small plugin to add a personal feature.
The usage it quite simple :
$ pylint mypackage.mymodule
This command will output all the errors and warnings related to the tested code (here : mypackage.mymodule), will dump a little summary at the end, and will give a mark to the tested code.
Pylint is free software distributed under the GNU Public Licence.
Home page --------- http://www.logilab.org/projects/pylint
Download -------- ftp://ftp.logilab.org/pub/pylint
Mailing list ------------ mailto://email@example.com