Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | testing/pylint: upgrade to 1.1.0 | Fabian Affolter | 2014-03-11 | 1 | -7/+7 |
| | |||||
* | testing/pylint: deps update | Fabian Affolter | 2013-09-17 | 1 | -3/+3 |
| | |||||
* | testing/pylint: upgrade to 1.0.0 | Fabian Affolter | 2013-09-08 | 1 | -4/+4 |
| | |||||
* | testing/pylint: upgrade to 0.28.0 | Fabian Affolter | 2013-06-15 | 1 | -2/+4 |
| | |||||
* | testing/pylint: upgrade to 0.26.0 | Fabian Affolter | 2013-01-08 | 1 | -2/+2 |
| | |||||
* | testing/pylint: upgrade to 0.25.2 | Fabian Affolter | 2012-09-21 | 1 | -2/+2 |
| | |||||
* | testing/pylint: upgrade to 0.25.1 | Fabian Affolter | 2012-05-20 | 1 | -2/+2 |
| | |||||
* | Initial APKBUILD for pylint | Fabian Affolter | 2011-12-03 | 1 | -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. |