Jump to content

Pylint: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Add GNU Emacs to list of example supported editors
m wikilink GNU EMacs
Line 23: Line 23:
It is also equipped with the Pyreverse module that allows [[Unified Modeling Language|UML]] diagrams to be generated from Python code.
It is also equipped with the Pyreverse module that allows [[Unified Modeling Language|UML]] diagrams to be generated from Python code.


It can be used as a stand-alone program, but also integrates with [[integrated development environment|IDEs]] such as [[Eclipse (software)|Eclipse]] with [[PyDev]]<ref>{{cite web |url=http://www.pydev.org/manual_adv_pylint.html |title=PyLint |website=Pydev.org |date=2016-10-31 |accessdate=2016-11-16}}</ref> and [[Microsoft Visual Studio|Visual Studio]],<ref>{{cite web |url=https://marketplace.visualstudio.com/items?itemName=tht13.python |title=Python for VSCode – Visual Studio Marketplace |website=Marketplace.visualstudio.com |date= |accessdate=2016-11-16}}</ref> and editors such as [[Atom (text editor)|Atom]]<ref>{{cite web|url=https://atom.io/packages/linter-pylint|title=linter-pylint|accessdate=2016-11-17}}</ref>, GNU Emacs and [[Vim (text editor)|Vim]].
It can be used as a stand-alone program, but also integrates with [[integrated development environment|IDEs]] such as [[Eclipse (software)|Eclipse]] with [[PyDev]]<ref>{{cite web |url=http://www.pydev.org/manual_adv_pylint.html |title=PyLint |website=Pydev.org |date=2016-10-31 |accessdate=2016-11-16}}</ref> and [[Microsoft Visual Studio|Visual Studio]],<ref>{{cite web |url=https://marketplace.visualstudio.com/items?itemName=tht13.python |title=Python for VSCode – Visual Studio Marketplace |website=Marketplace.visualstudio.com |date= |accessdate=2016-11-16}}</ref> and editors such as [[Atom (text editor)|Atom]]<ref>{{cite web|url=https://atom.io/packages/linter-pylint|title=linter-pylint|accessdate=2016-11-17}}</ref>, [[GNU Emacs]] and [[Vim (text editor)|Vim]].


It has received favourable reviews.<ref>{{cite web |author=José Castro |url=http://blog.codacy.com/2016/01/08/review-of-python-static-analysis-tools/ |title=Review of Python Static Analysis Tools – Codacy &#124; Blog |website=Blog.codacy.com |date= |accessdate=2016-11-16}} "Pylint is by far the best tool."</ref><ref>{{cite web |url=http://www.blog.pythonlibrary.org/2012/06/12/pylint-analyzing-python-code/ |title=PyLint: Analyzing Python Code &#124; The Mouse Vs. The Python |website=Blog.pythonlibrary.org |date=2012-06-12 |accessdate=2016-11-16}} "pylint is probably the most popular".</ref><ref>{{cite web |url=https://blog.jetbrains.com/pycharm/2014/06/write-clean-professional-maintainable-quality-code-in-python/ |title=Write Clean, Professional, Maintainable, Quality Code in Python &#124; PyCharm Blog |website=Blog.jetbrains.com |date=2014-06-13 |accessdate=2016-11-16}} "Pylint is still the definitive tool for Python code analysis".</ref>
It has received favourable reviews.<ref>{{cite web |author=José Castro |url=http://blog.codacy.com/2016/01/08/review-of-python-static-analysis-tools/ |title=Review of Python Static Analysis Tools – Codacy &#124; Blog |website=Blog.codacy.com |date= |accessdate=2016-11-16}} "Pylint is by far the best tool."</ref><ref>{{cite web |url=http://www.blog.pythonlibrary.org/2012/06/12/pylint-analyzing-python-code/ |title=PyLint: Analyzing Python Code &#124; The Mouse Vs. The Python |website=Blog.pythonlibrary.org |date=2012-06-12 |accessdate=2016-11-16}} "pylint is probably the most popular".</ref><ref>{{cite web |url=https://blog.jetbrains.com/pycharm/2014/06/write-clean-professional-maintainable-quality-code-in-python/ |title=Write Clean, Professional, Maintainable, Quality Code in Python &#124; PyCharm Blog |website=Blog.jetbrains.com |date=2014-06-13 |accessdate=2016-11-16}} "Pylint is still the definitive tool for Python code analysis".</ref>

Revision as of 12:46, 6 January 2019

Pylint
Developer(s)Sylvain Thénault (Logilab S.A.)[1][2]
Initial release2001; 23 years ago (2001)
Stable release
1.8.4[3] / 30 September 2017; 7 years ago (2017-09-30)
Repository
LicenseGeneral Public License
Websitewww.pylint.org

Pylint is a source-code, bug and quality checker for the Python programming language. 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] and Visual Studio,[7] and editors such as Atom[8], GNU Emacs and Vim.

It has received favourable reviews.[9][10][11]

References

  1. ^ "Pylint User Manual – Pylint 2.0.0 documentation". Docs.pylint.org. Retrieved 2016-11-16.
  2. ^ Tobias Macey (2015-12-12). "Episode 35 – Sylvain Thénault on ASTroid". pythonpodcast.com. Retrieved 2016-11-17.
  3. ^ "Release pylint-1.8.4 – PyCQA/pylint – GitHub". Github.com. 2018-04-05. Retrieved 2018-04-15.
  4. ^ "PEP 8 – Style Guide for Python Code". Python.org. Retrieved 2016-11-16.
  5. ^ "pylint (analyzes Python source code looking for bugs and signs of poor quality)". Logilab.org. 2006-09-26. Retrieved 2016-11-16.
  6. ^ "PyLint". Pydev.org. 2016-10-31. Retrieved 2016-11-16.
  7. ^ "Python for VSCode – Visual Studio Marketplace". Marketplace.visualstudio.com. Retrieved 2016-11-16.
  8. ^ "linter-pylint". Retrieved 2016-11-17.
  9. ^ José Castro. "Review of Python Static Analysis Tools – Codacy | Blog". Blog.codacy.com. Retrieved 2016-11-16. "Pylint is by far the best tool."
  10. ^ "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".
  11. ^ "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".
Stub icon

This free and open-source software article is a stub. You can help Wikipedia by expanding it.

Stub icon

This programming-tool-related article is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Pylint&oldid=877081034"