Łukasz Langa
Łukasz Langa
In general I am in favor of making this less noisy. If we can detect that the user does something reasonable, we shouldn't warn. So I'm open to pull requests...
All of your proposed changes sound good to me.
The typo will not work in third-party `mock` 2.0 and `unittest.mock` in 3.5+, it will reject unknown assert, assret, etc. methods. You shouldn't be developing new code on Python 3.4,...
There's nothing inherently wrong with the use of `eval`. What would you like the warning to say?
I changed handling of it to require explicit selection because "enable-extension" doesn't work as expected. Note that with 16.12.1 you don't have to "enable-extensions" at all. It's enough for you...
I haven't really looked too long for why enabled extensions don't work. I'd accept a pull request with a fix.
This is a flake8 plugin I would use! But it should be on an opt-in basis because it presents a design problem, not a clear-cut error. As such, it doesn't...
Similarly to #55, I would use this but it doesn't belong to pyflakes on the basis of not reporting an actual error. A superfluous import is absolutely harmless and a...
@bitglue, by a superfluous import I mean the exact case covered by this pull request, e.g. an import done within the function scope, when a module-level import has already been...