Pylint

Short description: Python static code analysis tool

Pylint

Developer(s)| Sylvain Thénault (Logilab S.A.)[1][2]
Initial release| 2001; 25 years ago (2001)
Written in| Python
License| General Public License
Website| pylint.pycqa.org

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.[3] 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.[4]

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,[5] Spyder and Visual Studio Code,[6] and editors such as Atom,[7] GNU Emacs and Vim.

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

## References

1. ↑ "Pylint User Manual – Pylint 2.0.0 documentation". http://docs.pylint.org/faq.html#who-wrote-pylint. Retrieved 2016-11-16.
2. ↑ Tobias Macey (2015-12-12). "Episode 35 – Sylvain Thénault on ASTroid". http://pythonpodcast.com/sylvain-thenault-astroid.html. Retrieved 2016-11-17.
3. ↑ "PEP 8 – Style Guide for Python Code". https://www.python.org/dev/peps/pep-0008/. Retrieved 2016-11-16.
4. ↑ "pylint (analyzes Python source code looking for bugs and signs of poor quality)". 2006-09-26. http://www.logilab.org/project/pylint. Retrieved 2016-11-16.
5. ↑ "PyLint". 2016-10-31. http://www.pydev.org/manual_adv_pylint.html. Retrieved 2016-11-16.
6. ↑ "Python for VSCode – Visual Studio Marketplace". https://marketplace.visualstudio.com/items?itemName=tht13.python. Retrieved 2016-11-16.
7. ↑ "linter-pylint". https://atom.io/packages/linter-pylint. Retrieved 2016-11-17.
8. ↑ José Castro (8 January 2016). "Review of Python Static Analysis Tools – Codacy | Blog". http://blog.codacy.com/2016/01/08/review-of-python-static-analysis-tools/. Retrieved 2016-11-16. "Pylint is by far the best tool."
9. ↑ "PyLint: Analyzing Python Code | The Mouse Vs. The Python". 2012-06-12. http://www.blog.pythonlibrary.org/2012/06/12/pylint-analyzing-python-code/. Retrieved 2016-11-16. "pylint is probably the most popular".
10. ↑ "Write Clean, Professional, Maintainable, Quality Code in Python | PyCharm Blog". 2014-06-13. https://blog.jetbrains.com/pycharm/2014/06/write-clean-professional-maintainable-quality-code-in-python/. Retrieved 2016-11-16. "Pylint is still the definitive tool for Python code analysis".

## External links

* on GitHub

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Pylint. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Pylint&oldid=685545"