Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #8267

Re: static analysis and other tools for checking Python code

Show key headers only | View raw

/Disclaimer: I started pylint with Sylvain Thénault back in 2001, but
the project has had new maintainers for a few years./

On Thu, Mar 03, 2016 at 08:06:52AM +0800, Paul Wise wrote:
> On Wed, Mar 2, 2016 at 9:23 PM, Nicolas Chauvat wrote:
> 
> > Maybe add pylint?
> 
> As I understand it:
> 
> pylint runs code from the source tree so it isn't suitable for running
> by default as that could be a security issue for people reviewing
> potentially untrusted code.

That would be https://pypi.python.org/pypi/PyChecker

Pylint has never run code from the source tree.

> pylint isn't able to be run automatically, it needs a human to come up
> with the right command-line.

"pylint <themodule>" should work fine.

Tuning pylint to a specific coding or project requires human action.

One option is to run "pylint -E <themodule>" to look only for
errors. This is also faster.

> [Paul Tagliamonte] flake8 has the most mindshare

That's not what google trends says

  https://www.google.fr/trends/explore#q=flake8%2C%20pylint%2C%20pyflakes&cmpt=q&tz=Etc%2FGMT-1

I included pyflakes because flake8's doc says "Flake8 is a wrapper around
PyFlakes, pep8 and Ned Batchelder’s McCabe script".
	    
The "Design Principles" section from pyflakes' doc states:

  """Pyflakes is also faster than Pylint or Pychecker. This is largely
  because Pyflakes only examines the syntax tree of each file
  individually. As a consequence, Pyflakes is more limited in the types
  of things it can check."""

To get the list of all the things your installed version of pylint can check for:

  pylint --list-msgs
  
Github stats prove the pylint project is pretty active

  https://github.com/PyCQA/pylint/graphs/contributors

-- 
Nicolas Chauvat

logilab.fr - services en informatique scientifique et gestion de connaissances  

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

static analysis and other tools for checking Python code Paul Wise <pabs@debian.org> - 2016-03-02 04:30 +0100
  Re: static analysis and other tools for checking Python code Scott Kitterman <debian@kitterman.com> - 2016-03-02 05:40 +0100
    Re: static analysis and other tools for checking Python code Paul Wise <pabs@debian.org> - 2016-03-02 06:00 +0100
  Re: static analysis and other tools for checking Python code Nicolas Chauvat <nicolas.chauvat@logilab.fr> - 2016-03-02 15:20 +0100
    Re: static analysis and other tools for checking Python code Paul Wise <pabs@debian.org> - 2016-03-03 01:10 +0100
      Re: static analysis and other tools for checking Python code "Paul R. Tagliamonte" <paultag@gmail.com> - 2016-03-03 01:30 +0100
      Re: static analysis and other tools for checking Python code Nicolas Chauvat <nicolas.chauvat@logilab.fr> - 2016-03-03 13:00 +0100
        Re: static analysis and other tools for checking Python code Paul Wise <pabs@debian.org> - 2016-03-04 06:10 +0100
          Re: static analysis and other tools for checking Python code Nicolas Chauvat <nicolas.chauvat@logilab.fr> - 2016-03-04 10:30 +0100
            Re: static analysis and other tools for checking Python code Paul Wise <pabs@debian.org> - 2016-03-04 14:40 +0100
              Re: static analysis and other tools for checking Python code Nicolas Chauvat <nicolas.chauvat@logilab.fr> - 2016-03-04 16:20 +0100
                Re: static analysis and other tools for checking Python code Paul Wise <pabs@debian.org> - 2016-03-05 04:20 +0100
                Re: static analysis and other tools for checking Python code Nicolas Chauvat <nicolas.chauvat@logilab.fr> - 2016-03-05 15:10 +0100
                Re: static analysis and other tools for checking Python code Paul Wise <pabs@debian.org> - 2016-03-06 10:20 +0100
  Re: static analysis and other tools for checking Python code Paul Wise <pabs@debian.org> - 2016-03-03 01:40 +0100
    Re: static analysis and other tools for checking Python code Jeremy Stanley <fungi@yuggoth.org> - 2016-03-03 01:50 +0100
    Re: static analysis and other tools for checking Python code Daniel Stender <stender@debian.org> - 2016-03-04 15:40 +0100
      Re: static analysis and other tools for checking Python code Paul Wise <pabs@debian.org> - 2016-03-05 04:10 +0100
  Re: static analysis and other tools for checking Python code Jeremy Stanley <fungi@yuggoth.org> - 2016-03-03 01:40 +0100

csiph-web