 | |
| Developer(s) | Sylvain Thénault (Logilab S.A.) [1] [2] |
|---|---|
| Initial release | 2001 |
| Stable release | 3.2.6
[3]
/ 21 July 2024 |
| Repository | |
| Written in | Python |
| License | General Public License |
| Website |
pylint |
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]
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.
It has received favourable reviews. [9] [10] [11]
- ^ "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.2.6". 21 July 2024. Retrieved 26 July 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.
- ^ José Castro (8 January 2016). "Review of Python Static Analysis Tools – Codacy | Blog". Blog.codacy.com. Retrieved 2016-11-16. "Pylint is by far the best tool."
- ^ "PyLint: Analyzing Python Code | The Mouse Vs. The Python". Blog.pythonlibrary.org. 2012-06-12. Retrieved 2016-11-16. "pylint is probably the most popular".
- ^ "Write Clean, Professional, Maintainable, Quality Code in Python | PyCharm Blog". Blog.jetbrains.com. 2014-06-13. Retrieved 2016-11-16. "Pylint is still the definitive tool for Python code analysis".
.svg){kind=logo} | This free and open-source software article is a stub. You can help Wikipedia by expanding it. |
 | This programming-tool-related article is a stub. You can help Wikipedia by expanding it. |
|
| |
| Developer(s) | Sylvain Thénault (Logilab S.A.) [1] [2] |
|---|---|
| Initial release | 2001 |
| Stable release | 3.2.6
[3]
/ 21 July 2024 |
| Repository | |
| Written in | Python |
| License | General Public License |
| Website |
pylint |
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]
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.
It has received favourable reviews. [9] [10] [11]
- ^ "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.2.6". 21 July 2024. Retrieved 26 July 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.
- ^ José Castro (8 January 2016). "Review of Python Static Analysis Tools – Codacy | Blog". Blog.codacy.com. Retrieved 2016-11-16. "Pylint is by far the best tool."
- ^ "PyLint: Analyzing Python Code | The Mouse Vs. The Python". Blog.pythonlibrary.org. 2012-06-12. Retrieved 2016-11-16. "pylint is probably the most popular".
- ^ "Write Clean, Professional, Maintainable, Quality Code in Python | PyCharm Blog". Blog.jetbrains.com. 2014-06-13. Retrieved 2016-11-16. "Pylint is still the definitive tool for Python code analysis".
|
| This free and open-source software article is a stub. You can help Wikipedia by expanding it. |
|
| This programming-tool-related article is a stub. You can help Wikipedia by expanding it. |