diff options
author | root <none@none> | 2006-04-26 10:48:09 +0000 |
---|---|---|
committer | root <none@none> | 2006-04-26 10:48:09 +0000 |
commit | 4becf6f9e596b45401680c4947e2d92c953d5e08 (patch) | |
tree | 3bb03a16daa8c780bf60c622dc288eb01cfca145 /announce.txt | |
download | pylint-git-4becf6f9e596b45401680c4947e2d92c953d5e08.tar.gz |
forget the past.
forget the past.
Diffstat (limited to 'announce.txt')
-rw-r--r-- | announce.txt | 42 |
1 files changed, 42 insertions, 0 deletions
diff --git a/announce.txt b/announce.txt new file mode 100644 index 000000000..4f49abe0c --- /dev/null +++ b/announce.txt @@ -0,0 +1,42 @@ +What's new ? +------------ +%CHANGELOG% + + +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 +--------- +%WEB% + +Download +-------- +%FTP% + +Mailing list +------------ +%MAILINGLIST% |