summaryrefslogtreecommitdiff
path: root/dev-python/pylint/metadata.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2017-10-09 18:53:29 +0100
committerV3n3RiX <venerix@redcorelinux.org>2017-10-09 18:53:29 +0100
commit4f2d7949f03e1c198bc888f2d05f421d35c57e21 (patch)
treeba5f07bf3f9d22d82e54a462313f5d244036c768 /dev-python/pylint/metadata.xml
reinit the tree, so we can have metadata
Diffstat (limited to 'dev-python/pylint/metadata.xml')
-rw-r--r--dev-python/pylint/metadata.xml23
1 files changed, 23 insertions, 0 deletions
diff --git a/dev-python/pylint/metadata.xml b/dev-python/pylint/metadata.xml
new file mode 100644
index 000000000000..4fd10546d5c7
--- /dev/null
+++ b/dev-python/pylint/metadata.xml
@@ -0,0 +1,23 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="project">
+ <email>python@gentoo.org</email>
+ <name>Python</name>
+ </maintainer>
+ <longdescription lang="en">
+ Pylint is a Python source code analyzer which looks for programming errors,
+ helps enforcing a coding standard and sniffs for some code smells (as
+ defined in Martin Fowler's Refactoring book). Pylint can be seen as
+ another PyChecker since nearly all tests you can do with PyChecker can also
+ be done with Pylint. However, Pylint offers some more features, like
+ checking length of lines of code, checking if variable names are
+ well-formed according to your coding standard, or checking if declared
+ interfaces are truly implemented, and much more. Additionally, it is
+ possible to write plugins to add your own checks.
+ </longdescription>
+ <upstream>
+ <remote-id type="pypi">pylint</remote-id>
+ <remote-id type="github">pycqa/pylint</remote-id>
+ </upstream>
+</pkgmetadata>