PEP8 code cleanup support offer

Hi,

I browsed the code on github and noticed a relatively high number of PEP8 violations in Python files. Do you guys need help cleaning up that stuff? I could do it if you wish.

Most of the violations that PyCharm IDE reports are relatively simple problems: use of tabs, lines too long (>120 chars), variable names in Camelcase, variable names that hide built-in keywords (dir, type, file etc..., these can be suffixed by an underscore dir_, type_, file_), unused variables or arguments, use of unnecessary brackets in if statements ( "if (condition): pass", instead of "if condition: pass" ), vertical spacing gets too wide at times, and so on... these are relatively boring "no-brainers", that I can do them even without understanding the code. This stuff could go into one commit, it can be summed up as only white space changes and variable rename operations.

Into second commit I could put basic stuff that touches code execution logic. Like there are some issues that are not exactly errors, but should be reformatted anyway: "if not var in container:" should be "if var not in container:" I am quite experienced with Python, so this should be done without any errors, but just in case I do make an error and this commit should be reversed, it would be smart to separate it from first commit that does not touch code execution logic.

I might need some help with second commit. For example which Python version are you using (2 or 3)? This affects things like "super()" syntax, or class definition (should they subclass "object"), or I noticed some places where methods are defined like this:

# not the real code, just a simplification !!

def method(self, agr1, *args):
    return arg1 ** 2

In this case *args tuple is useless, and it might be a coding error, but it also might be put in there as a protection in case "method" is called with more that one argument. I can prepare a list of such ambiguous code samples, and you can decide what to do in each case. Small refactoring would also be needed in cases where "private" attributes (private in the sense that they names start with underscore) are accessed directly, or in case where data attributes are created outside of __init__(self).

In case you are interested, let me know, I could start this weekend.

There is one problem though, I know nothing of launchpad or its revision system. Could you give me few pointers how to get the latest code from launchpad (if github mirror is not synchronized on daily bases), and how do I push the code back to you?

Thank you and best regards,
Ivan