Pylint is a static code analysis tool for the Python programming language. It is named following a common convention in Python of a "py" prefix, and a nod to the C programming lint program. It follows the style recommended by PEP 8, the Python style guide.[4] It is similar to Pychecker and Pyflakes, but includes the following features:
- Checking the length of each line
- Checking that variable names are well-formed according to the project's coding standard
- Checking that declared interfaces are truly implemented.[5]
Developer(s) | Sylvain Thénault (Logilab S.A.)[1][2] |
---|---|
Initial release | 2001 |
Stable release | 3.3.1[3]
/ 24 September 2024 |
Repository | |
Written in | Python |
License | General Public License |
Website | pylint |
It is also equipped with the Pyreverse module that allows UML diagrams to be generated from Python code.
It can be used as a stand-alone program, but also integrates with IDEs such as Eclipse with PyDev,[6] Spyder and Visual Studio Code,[7] and editors such as Atom,[8] GNU Emacs and Vim.
References
edit- ^ "Pylint User Manual – Pylint 2.0.0 documentation". Docs.pylint.org. Retrieved 2016-11-16.
- ^ Tobias Macey (2015-12-12). "Episode 35 – Sylvain Thénault on ASTroid". pythonpodcast.com. Retrieved 2016-11-17.
- ^ "Release 3.3.1". 24 September 2024. Retrieved 26 September 2024.
- ^ "PEP 8 – Style Guide for Python Code". Python.org. Retrieved 2016-11-16.
- ^ "pylint (analyzes Python source code looking for bugs and signs of poor quality)". Logilab.org. 2006-09-26. Retrieved 2016-11-16.
- ^ "PyLint". Pydev.org. 2016-10-31. Retrieved 2016-11-16.
- ^ "Python for VSCode – Visual Studio Marketplace". Marketplace.visualstudio.com. Retrieved 2016-11-16.
- ^ "linter-pylint". Retrieved 2016-11-17.