aboutsummaryrefslogtreecommitdiff
path: root/development/pylint/README
diff options
context:
space:
mode:
authorgrissiom <chaos.proton@gmail.com>2010-05-12 23:28:49 +0200
committerDavid Somero <xgizzmo@slackbuilds.org>2010-05-12 23:28:49 +0200
commit0ab3886b595a7960108a4fa48b737b3598a076ef (patch)
tree3f6a524055f7e95734f4fef11d4f1d9b4c15e9d9 /development/pylint/README
parentd8f529d95beef6916a802f3a0365146e4f1c9cc4 (diff)
development/pylint: Added to 12.2 repository
Diffstat (limited to 'development/pylint/README')
-rw-r--r--development/pylint/README11
1 files changed, 11 insertions, 0 deletions
diff --git a/development/pylint/README b/development/pylint/README
new file mode 100644
index 0000000000000..aa7f9871210e4
--- /dev/null
+++ b/development/pylint/README
@@ -0,0 +1,11 @@
+Pylint is a python tool that checks if a module satisfies 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 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.
+
+Dependences: logilab-astng, logilab-common available at SlackBuilds.org