Upstream software project

pylint

Syntax and style checker for Python code

About pylint

Syntax and style checker for Python code

This project links 7 native package records across 4 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

pylint repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 2 package records; Fedora 44: 2 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.pylint: recorded package coverageFedora 432 recordsFedora 442 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
pylint
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
fedora-43, fedora-44, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-2.0-or-later
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Pylint analyzes Python source code looking for bugs and signs of poor quality. Pylint is a python tool that checks if a module satisfies a coding standard. Pylint can be seen as another PyChecker since nearly all tests you can do with PyChecker can also be done with Pylint. But Pylint offers some 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 (see the complete check list). 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.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package pylint

    43 (Fedora 43) (Unspecified): Analyzes Python code looking for bugs and signs of poor quality

    3.3.9-2.fc43: noarch

    Source: pylint

  2. Package python3-pylint

    43 (Fedora 43) (Unspecified): Analyzes Python code looking for bugs and signs of poor quality

    3.3.9-2.fc43: noarch

    Source: pylint

Fedora 44

  1. Package pylint

    44 (Fedora 44) (Unspecified): Analyzes Python code looking for bugs and signs of poor quality

    4.0.5-1.fc44: noarch

    Source: pylint

  2. Package python3-pylint

    44 (Fedora 44) (Unspecified): Analyzes Python code looking for bugs and signs of poor quality

    4.0.5-1.fc44: noarch

    Source: pylint

openSUSE Leap 16.0

  1. Package python313-pylint

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Syntax and style checker for Python code

    3.3.7-160000.2.2: noarch

    Source: python-pylint

openSUSE Tumbleweed

  1. Package python313-pylint

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Syntax and style checker for Python code

    4.0.7-1.1: noarch

    Source: python-pylint

  2. Package python314-pylint

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Syntax and style checker for Python code

    4.0.7-1.1: noarch

    Source: python-pylint

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.