Gentoo Packages

Search

Package Information

Description:

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.

Homepage:

https://pypi.org/project/pylint/ https://github.com/pylint-dev/pylint/

License:

GPL-2

Versions

Metadata

Description

• 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.

Maintainers

• Python (python@gentoo.org) - Type: project

Upstream

• Remote IDs:
  • pypi: pylint
  • github: pylint-dev/pylint

<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>
	<stabilize-allarches></stabilize-allarches>
	<upstream>
		<remote-id type="pypi">pylint</remote-id>
		<remote-id type="github">pylint-dev/pylint</remote-id>
	</upstream>
</pkgmetadata>

Lint Warnings

• [Warning] Ebuild 4.0.5 uses IUSE flag 'examples' which is not documented in metadata.xml. Add the flag to metadata.xml <use> section.
• [Warning] Ebuild 4.0.4-r1 uses IUSE flag 'examples' which is not documented in metadata.xml. Add the flag to metadata.xml <use> section.
• [Warning] Ebuild 4.0.4 uses IUSE flag 'examples' which is not documented in metadata.xml. Add the flag to metadata.xml <use> section.
• [Warning] Missing md5-cache for version 4.0.5. Run 'ebuild <ebuild_file> manifest' or 'egencache' to generate it.
• [Warning] Missing md5-cache for version 4.0.4-r1. Run 'ebuild <ebuild_file> manifest' or 'egencache' to generate it.
• [Warning] Missing md5-cache for version 4.0.4. Run 'ebuild <ebuild_file> manifest' or 'egencache' to generate it.

USE Flags

Manifest