aboutsummaryrefslogtreecommitdiffstats
path: root/testing/pylint
Commit message (Collapse)AuthorAgeFilesLines
* testing/pylint: upgrade to 1.4.3Fabian Affolter2015-03-291-4/+4
|
* testing/pylint: fix checksumsNatanael Copa2015-03-111-3/+3
|
* testing/pylint: upgrade to 1.4.1Fabian Affolter2015-03-111-1/+1
|
* testing/pylint: upgrade to 1.4.0Fabian Affolter2014-11-271-5/+5
|
* testing/pylint: upgrade to 1.3.0Fabian Affolter2014-08-231-5/+5
|
* testing/pylint: upgrade to 1.2.1Fabian Affolter2014-07-071-4/+4
|
* testing/pylint: upgrade to 1.1.0Fabian Affolter2014-03-111-7/+7
|
* testing/pylint: deps updateFabian Affolter2013-09-171-3/+3
|
* testing/pylint: upgrade to 1.0.0Fabian Affolter2013-09-081-4/+4
|
* testing/pylint: upgrade to 0.28.0Fabian Affolter2013-06-151-2/+4
|
* testing/pylint: upgrade to 0.26.0Fabian Affolter2013-01-081-2/+2
|
* testing/pylint: upgrade to 0.25.2Fabian Affolter2012-09-211-2/+2
|
* testing/pylint: upgrade to 0.25.1Fabian Affolter2012-05-201-2/+2
|
* Initial APKBUILD for pylintFabian Affolter2011-12-031-0/+34
Package description: Pylint is a python tool that checks if a module satisfies a coding standard. Pylint is similar to PyChecker but offers 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. 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.