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

Re: static analysis and other tools for checking Python code

From	Paul Wise <pabs@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: static analysis and other tools for checking Python code
Date	2016-03-04 06:10 +0100
Message-ID	<r8Q9X-1D7-3@gated-at.bofh.it> (permalink)
References	<r8Q9X-1D7-5@gated-at.bofh.it> <r85E5-1TO-1@gated-at.bofh.it> <r8fN7-l3-3@gated-at.bofh.it> <r8p06-7eU-13@gated-at.bofh.it> <r8A5e-6Bm-45@gated-at.bofh.it>
Organization	Debian

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Thu, 2016-03-03 at 12:52 +0100, Nicolas Chauvat wrote:

> That would be https://pypi.python.org/pypi/PyChecker
> 
> Pylint has never run code from the source tree.

I wonder where I got that impression from.

What about from the module it is checking?

> "pylint <themodule>" should work fine.

Unfortunately that needs the module installed to work.

Is there any way to make it scan the source tree instead?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

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