Add support for ignoring some warnings about pyflakes

[pyflakes-bot]

Original comment by exarkun (@exarkun?) on Launchpad:

---

I'd rather fix the bugs in pyflakes that lead to spurious warnings.

[pyflakes-bot]

Original comment by bukzor on Launchpad:

---

We have some questionable-but-necessary code which uses globals().update(). The of course causes pyflakes to freak out about undefined variables. I'd like to be able to ignore those warnings, instead of ignoring pyflakes altogether.

[pyflakes-bot]

Original comment by esz-michel on Launchpad:

---

@sinzui: Can you link to the changeset? I am curious to see how this was implemented. Sorry if the link is already available somewhere, but I could noit find it :\

I would really like this feature as well, but more fine-grained as proposed. For example, pylint allows you to disable a specific error-code (see http://www.logilab.org/card/pylint_manual#messages-control). Or, the Java @SuppressWarnings annotation also allows you to ignore specific warnings.

I find the proposed solution to simply ignore pyflakes altogether is a bit like a "except Exception": You might miss other errors ;)

[pyflakes-bot]

Original comment by sinzui on Launchpad:

---

Adi extended PyFlakesChecker to accept the raw text of the module being checked. The report() method looks of the line number of warning/error and in the text and looks for "# pyflakes:ignore". The report returns early if the comment is present.
https://code.launchpad.net/~adiroiban/pocket-lint/907742/+merge/102882

[pyflakes-bot]

Original comment by adiroiban (@adiroiban?) on Launchpad:

---

Hi,

Right now, pyflakes messages do not have a ID for each message class. In pylint each message class has its own ID.

I agree that this all or nothing filter can lead to other troubles. I will check to see if pyflakes developers would like to accept a patch to pyflakes to add IDs for each message class, and then we can improve the current pocketlint filter.

[pyflakes-bot]

Original comment by bukzor on Launchpad:

---

Alternative solution: use a pylintrc that is only roughly as picky as pyflakes.

[pyflakes-bot]

Original comment by glyph on Launchpad:

---

There's already a bug for automatically detecting the entirely detectable class of error in the example here, isn't there? It would be so much nicer to do that than to encourage users to drop these comment turds into their code.

[pyflakes-bot]

Original comment by exarkun (@exarkun?) on Launchpad:

---

More than one:

https://bugs.launchpad.net/pyflakes/+bug/885140
https://bugs.launchpad.net/pyflakes/+bug/800691
https://bugs.launchpad.net/pyflakes/+bug/916264

Probably others. Fixing these real problems would be a great win for all pyflakes users.

[pyflakes-bot]

Original comment by florent.x (@florentx?) on Launchpad:

---

Issues 800691 and 916264 and many others were fixed with Pyflakes 0.6.1.

If you really want to use comments to disable some checks, try Flake8.

But the recommended path is to open an issue if it looks like a limitation of Pyflakes.