On Tue, Mar 20, 2007 at 08:48:46PM -0600, Charles R Harris wrote:
> On 3/20/07, Pierre GM <[EMAIL PROTECTED]> wrote:
> >
> >On Tuesday 20 March 2007 15:29:01 Charles R Harris wrote:
> >> but I want
> >> to suggest that we run pychecker, and maybe pylint, over the python code
> >to
> >> look for err
On 3/20/07, Pierre GM <[EMAIL PROTECTED]> wrote:
On Tuesday 20 March 2007 15:29:01 Charles R Harris wrote:
> but I want
> to suggest that we run pychecker, and maybe pylint, over the python code
to
> look for errors.
I'm using Pydev w/ Eclipse that supports pylint. I usually don't have any
warn
On Tuesday 20 March 2007 15:29:01 Charles R Harris wrote:
> but I want
> to suggest that we run pychecker, and maybe pylint, over the python code to
> look for errors.
I'm using Pydev w/ Eclipse that supports pylint. I usually don't have any
warning from pylint about numpy. Could you be more spec
All,
I've run pychecker on some of my programs that import numpy and it issues
many warnings about numpy. Many (most?) of the warnings look bogus, but some
also look valid. I will try to work through some of these, but I want to
suggest that we run pychecker, and maybe pylint, over the python cod
