Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8273
| From | Nicolas Chauvat <nicolas.chauvat@logilab.fr> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: static analysis and other tools for checking Python code |
| Date | 2016-03-04 16:20 +0100 |
| Message-ID | <r8ZGi-7O-3@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <r8p06-7eU-13@gated-at.bofh.it> <r8A5e-6Bm-45@gated-at.bofh.it> <r8Q9X-1D7-3@gated-at.bofh.it> <r8UdA-4zt-21@gated-at.bofh.it> <r8Y7w-7tk-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Mar 04, 2016 at 09:33:17PM +0800, Paul Wise wrote: > Do you know if pylint can recursively scan for Python files rather > than being passed the names of Python files? It does recursively scan for Python files: $ tree bar/ bar/ ├── baz │ ├── gloo.py │ └── __init__.py ├── foo.py └── __init__.py $ cat bar/**/*py b = a-1 a = b+1 $ pylint -E bar/ No config file found, using default configuration ************* Module bar.foo E: 1, 4: Undefined variable 'b' (undefined-variable) ************* Module bar.baz.gloo E: 1, 4: Undefined variable 'a' (undefined-variable) > Incidentally, I got a patch for c-a-t-t to support pylint from the > author of yamllint: > > https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git/patch/?id=4dc0a9ca929fa3488ab93cb4e997101d52bbe8a8 Nice! -- 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
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