As of PyDev 2.3.0, pep8 is integrated in PyDev by default, even shipping with a default version of it. Open Window > Preferences It must be enabled in PyDev > Editor > Code Analysis > pep8.py Errors/Warnings should be shown as markers (as other things in the regular code analysis). In the event a file … Read more
The current version of pylint now does this, and reports it as error class C0411.
As far as I know, you can’t. You can disable errors or warnings user wide, or per project. See the documentation. Instead, you can use the # noqa comment at the end of a line, to skip that particular line (see patch 136). Of course, that would skip all PEP8 errors. The main author argues … Read more
An example is given in PEP 8: class Rectangle(Blob): def __init__(self, width, height, color=”black”, emphasis=None, highlight=0): So that is the official answer. Personally I detest this approach, in which continuation lines have leading whitespace that doesn’t correspond to any real indentation level. My approach would be: class Rectangle(Blob): def __init__( self, width, height, color=”black”, emphasis=None, … Read more
This is not actually a PEP8 violation. I simply do this: from .my_class import MyClass # noqa Edit: Another possibility is to use __all__. In that case, flake8 understands what is going on: from .my_class import MyClass __all__ = [‘MyClass’,]
It’s almost always better to specify an explicit exception type. If you use a naked except: clause, you might end up catching exceptions other than the ones you expect to catch – this can hide bugs or make it harder to debug programs when they aren’t doing what you expect. For example, if you’re inserting … Read more
If there are just a few imports, you can just ignore PEP8 on those import lines: import sys sys.path.insert(“..”, 0) import my_module # noqa: E402
[x for x in (1,2,3) ] works fine, so you can pretty much do as you please. I’d personally prefer [something_that_is_pretty_long for something_that_is_pretty_long in somethings_that_are_pretty_long] The reason why \ isn’t appreciated very much is that it appears at the end of a line, where it either doesn’t stand out or needs extra padding, which has … Read more
I guess that it is because a keyword argument is essentially different than a variable assignment. For example, there is plenty of code like this: kw1 = some_value kw2 = some_value kw3 = some_value some_func( 1, 2, kw1=kw1, kw2=kw2, kw3=kw3) As you see, it makes complete sense to assign a variable to a keyword argument … Read more
You can use autopep8! Whilst you make yourself a cup of coffee this tool happily removes all those pesky PEP8 violations which don’t change the meaning of the code. Install it via pip: pip install autopep8 Apply this to a specific file: autopep8 py_file –in-place or to your project (recursively), the verbose option gives you … Read more