Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #72679
| Newsgroups | comp.lang.python |
|---|---|
| Date | 2014-06-04 22:12 -0700 |
| References | <roy-05CD0E.20134129052014@news.panix.com> |
| Message-ID | <ffa77644-c6fa-496d-91ec-54b1742317b7@googlegroups.com> (permalink) |
| Subject | Re: pyflakes best practices? |
| From | Miki Tebeka <miki.tebeka@gmail.com> |
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 supports ignoring certain lines by appending a comment starting with # NOQA HTH, -- Miki
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
pyflakes best practices? Roy Smith <roy@panix.com> - 2014-05-29 20:13 -0400
Re: pyflakes best practices? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-30 01:50 +0100
Re: pyflakes best practices? Roy Smith <roy@panix.com> - 2014-05-29 21:14 -0400
Re: pyflakes best practices? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-31 18:10 +0100
Re: pyflakes best practices? Roland Koebler <r.koebler@yahoo.de> - 2014-06-04 17:35 +0200
Re: pyflakes best practices? Miki Tebeka <miki.tebeka@gmail.com> - 2014-06-04 22:12 -0700
csiph-web