Greetings,
> So, what's the best practice here? How do people deal with the false
> positives? Is there some way to annotate the source code to tell
> pyflakes to ignore something?
We use flake8 (pyflakes + pep8) as pre step for the tests. We fail the tests on
any output from flake8.
flake8
- Original Message -
> We've recently started using pyflakes. The results seem to be
> similar
> to most tools of this genre. It found a few real problems. It
> generated a lot of noise about things which weren't really wrong, but
> were easy to fix (mostly, unused imports), and a few pl
Hi,
I would recommend to use Pylint (http://www.pylint.org/) in addition
to pyflakes. Pylint is much more powerful than pyflakes, and largely
configurable.
Regards
Roland
--
https://mail.python.org/mailman/listinfo/python-list
On 30/05/2014 02:14, Roy Smith wrote:
In article ,
Mark Lawrence wrote:
On 30/05/2014 01:13, Roy Smith wrote:
We've recently started using pyflakes. The results seem to be similar
to most tools of this genre. It found a few real problems. It
generated a lot of noise about things which we
In article ,
Mark Lawrence wrote:
> On 30/05/2014 01:13, Roy Smith wrote:
> > We've recently started using pyflakes. The results seem to be similar
> > to most tools of this genre. It found a few real problems. It
> > generated a lot of noise about things which weren't really wrong, but
> > w
On 30/05/2014 01:13, Roy Smith wrote:
We've recently started using pyflakes. The results seem to be similar
to most tools of this genre. It found a few real problems. It
generated a lot of noise about things which weren't really wrong, but
were easy to fix (mostly, unused imports), and a few p
