pep8

Based on PEP8 documentation, I was not able to find any reference regarding if I should use pass for aesthetic reasons on code. Based on the example below, should I keep those else or can I erase them? Until now, the main reason I'm keeping it is based on the mantra "Explicit is better than implicit." if fields: for i in foo: if i == 'something': print "something" else: pass else: pass Yes, you can/should remove them because they do nothing. The Python community teaches "explicit is better than implicit" as long as the explicit code does something useful. Those else: pass 's however contribute

I tried with #:PEP8 -E223 or # pep8: disable=E223 I thought the second would work but doesn't seems to work. Do you have an idea how I can handle this ? 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 against source file noise , so they suggested # pep8 comments don't get included. Note that there is also nopep8 , which is the equivalent. noqa (which

Searching for an answer on PyLint's mailing list brings no interesting results. PyLint is known to be very customizable so I guess this should be possible... The reason I would like PyLint to check compliance with PEP8 is because PyDev has much better support for PyLint than it has for PEP8. It's easier to have one tool doing all checks than having to use two. I also asked this question on PyLint's mailing list at http://thread.gmane.org/gmane.comp.python.logilab/1039 Example of diagnostic messages from PEP8 which I don't get from PyLint: E203 whitespace before ':' E225 missing whitespace

While searching through a Python project, I found a few lines commented with # noqa . import sys sys.path.append(r'C:\dev') import some_module # noqa What does noqa mean in Python? Is it specific to Python only? jimf Adding # noqa to a line indicates that the linter (a program that automatically checks code quality) should not check this line. Any warnings that code may have generated will be ignored. That line may have something that "looks bad" to the linter, but the developer understands and intends it to be there for some reason. For more information, see the Flake8 documentation for

I enabled PEP8 in my Eclipse Luna for a pydev project and it works if I create a new file but it doesn't work for an existing project/file. I enabled PEP8 in window> preferences > pydev > editor > codeAnalysis > pep8.py > warning and I tried to click right onto my project folder > pydev > code analysis But unfortunately it doesn't work. PyDev will only analyze valid packages in the PYTHONPATH (i.e.: under a source folder). So, Are your sources in the existing project under a source folder and are folders actually packages (i.e.: do they have __init__.py files?) See: http://pydev.org/manual_101

I need help choosing proper names for variables with long actual names. I have read pep8 docs, but I couln't find addressed such issue. Would you rename very_long_variable_name to something like vry_lng_var_nm or would you leave it as it is. I notice that pythons build in libraries have very short names and I'd like to follow the conventions if it exists for this case. I know I can name it something not very descriptive and add description, which would explain its meaning, but what do you think should be the variables name. PEP8 recommends short variable names, but achieving this requires good