S
Sylvain Thenault
Hi there,
I'm very pleased to announce the 0.6 release of PyLint. This release
fix a lot of bugs and should be much more stable than the 0.5 release
where stopping actual import of analyzed modules has been introduced
(and that's really a huge improvment, since this was potentialy
introducing some side effects). There are also more documentation,
a better test suite, and also minor new features was added. Every
users of pylint should update to 0.6. Notice that Logilab's common
library 0.9 is required (http://www.logilab.org/projects/common).
Enjoy !
What's new ?
------------
* refix pylint emacs mode
* no more traceback when just typing "pylint"
* fix a bug which may cause crashes on resolving parent classes
* fix problems with the format checker: don't chock on files
containing multiple CR, avoid C0322, C0323, C0324 false positives
with triple quoted string with quote inside
* correctly detect access to member defined latter in __init__ method
* now depends on common 0.8.1 to fix problem with interface resolution
(close #8606)
* new --list-msgs option describing available checkers and their
messages
* added windows specific documentation to the README file, contributed
by Brian van den Broek
* updated doc/features.txt (actually this file is now generated using
the --list-msgs option), more entries into the FAQ
* improved tests coverage
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/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
I'm very pleased to announce the 0.6 release of PyLint. This release
fix a lot of bugs and should be much more stable than the 0.5 release
where stopping actual import of analyzed modules has been introduced
(and that's really a huge improvment, since this was potentialy
introducing some side effects). There are also more documentation,
a better test suite, and also minor new features was added. Every
users of pylint should update to 0.6. Notice that Logilab's common
library 0.9 is required (http://www.logilab.org/projects/common).
Enjoy !
What's new ?
------------
* refix pylint emacs mode
* no more traceback when just typing "pylint"
* fix a bug which may cause crashes on resolving parent classes
* fix problems with the format checker: don't chock on files
containing multiple CR, avoid C0322, C0323, C0324 false positives
with triple quoted string with quote inside
* correctly detect access to member defined latter in __init__ method
* now depends on common 0.8.1 to fix problem with interface resolution
(close #8606)
* new --list-msgs option describing available checkers and their
messages
* added windows specific documentation to the README file, contributed
by Brian van den Broek
* updated doc/features.txt (actually this file is now generated using
the --list-msgs option), more entries into the FAQ
* improved tests coverage
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/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