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

Re: static analysis and other tools for checking Python code

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Paul Wise <pabs@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: static analysis and other tools for checking Python code
Date	Fri, 04 Mar 2016 06:10:01 +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>
X-Mailbox-Line	From debian-python-request@lists.debian.org Fri Mar 4 05:03:35 2016
Old-Return-Path	<pabs@debian.org>
X-Amavis-Spam-Status	No, score=-14.301 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Organization	Debian
Content-Type	multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-PA9YoWd0jP99q0C1w//Y"
X-Mailer	Evolution 3.18.3-1
MIME-Version	1.0
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/13596
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/1457067797.3193.13.camel@debian.org
Approved	robomod@news.nic.it
Lines	53
Sender	robomod@news.nic.it
X-Original-Date	Fri, 04 Mar 2016 13:03:17 +0800
X-Original-Message-ID	<1457067797.3193.13.camel@debian.org>
X-Original-References	<CAKTje6Hjp+RA666ey=mi7mwsTnxOor2LS85pSU7krziM0Z6=Yw@mail.gmail.com> <20160302132331.GB20628@volans.logilab.fr> <CAKTje6FQ1STcN3JDVtDvQ_o6cJ=tsr+dqWQN+G0g5HvTXQSjFg@mail.gmail.com> <20160303115203.GA3089@volans.logilab.fr>
Xref	csiph.com linux.debian.maint.python:8269

Show key headers only | 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