Basic PEP8 conformance now added and testable

[snark]

PEP8 is the Python code format standard; I've written a unittest-style test for everything in the code directories (you can run it with a simple "python tests/test_pep8" or the more elaborate run-everything "python -m unittest discover tests/"). I've further gone through and cleaned everything up so that it conforms to this standard; the heavy lifting was done with the autopep8 tool, which I have not included in the requirements-dev list but which may be useful for getting future changes to conform.

If the key devs on this (hi Leonard! hi Andy!) want to relax some of the PEP8 strictures, such as the 80-character limit on line length, we can add a pep8 config file.

[lhl]

@snark thx for the work. how relaxed can we go on pep8 tests? specific things:

• i really like the formatting for my from imports since they line up the module names, formatter removes that
• @waxpancake doesn't care too much and i'm pretty wedded to 2-space indents, mostly because i work on close-to 80char screens (small laptop)
• the current tester strips triple ### comments which we use to demarcate blocks (as opposed to single # which is for implementation comments)

[snark]

Looking this up: 2-space formatting is E114; triple # in block comments is E266; I think the import stuff is E401. Let me strongly encourage you to add a style guide note if you're wedded to 2-space indents, since 4-space is a very strong preference in the wider Python ecosystem, and contributors aren't going to be doing it.

Want me to add config to disable those checks and resubmit the pull rec?

[lhl]

Hey @snark sorry for losing track of this, last week got crazy. Mind disabling the checks as we talked about and resubmitting? I'll make a task to have a styleguide about 2-space indents.