aboutsummaryrefslogtreecommitdiffstats
path: root/testing/pylint
Commit message (Collapse)AuthorAgeFilesLines
* [various]: unify names of licenses according to SPDXJakub Jirutka2017-12-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit updates $license variable in all APKBUILDs to comply with short names specified by SPDX version 3.0 [1] where possible. It was done using find-and-replace method on substrings inside $license variables. Only license names were updated, not "expressions" specifying relation between the licenses (e.g. "X and Y", "X or Y", "X and (Y or Z)") or exceptions (e.g. "X with exceptions"). Many licenses have a version or multiple variants, e.g. MPL-2.0, BSD-2-Clause, BSD-3-Clause. However, $license in many aports do not contain license version or variant. Since there's no way how to infer this information just from abuild, it were left without the variant suffix or version, i.e. non SPDX compliant. GNU licenses (AGPL, GFDL, GPL, LGPL) are especially complicated. They exist in two variants: -only (formerly e.g. GPL-2.0) and -or-later (formerly e.g. GPL-2.0+). We did not systematically noted distinguish between these variants, so GPL-2.0, GPL2, GPLv2 etc. may mean GPL-2.0-only or GPL-2.0-or-later. Thus GNU licenses without "+" (e.g. GPL2+) were left without the variant suffix, i.e. non SPDX compliant. Note: This commit just fixes format of the license names, no verification has been done if the specified license information is actually correct! [1]: https://spdx.org/licenses/
* testing/pylint:added missing dependencies. Close #8110Francesco Colista2017-11-261-4/+4
|
* testing/pylint: upgrade to 1.7.4Roberto Oliveira2017-10-061-5/+3
|
* testing/pylint: rebuild against new version of python3Ɓukasz Jendrysik2017-02-181-1/+1
|
* testing/pylint: upgrade to 1.6.4 and enable py3Fabian Affolter2016-12-271-10/+30
|
* [various] rename python executable in APKBUILDs to python2Jakub Jirutka2016-10-261-2/+2
|
* [various] rename dependency python to python2Jakub Jirutka2016-10-261-1/+1
|
* [various] rename dependency python-dev to python2-devJakub Jirutka2016-10-261-1/+1
|
* testing/pylint: fix buildCarlo Landmeter2016-08-281-10/+3
|
* testing/*: change source URL pypi.python.org to files.pythonhosted.orgJakub Jirutka2016-07-081-1/+1
| | | | See https://bitbucket.org/pypa/pypi/issues/438/backwards-compatible-un-hashed-package#comment-27734791
* 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.