PEP 8 compliance

[Chris Ortner]

m-otteneder published a blueprint concerning this really important
issue (https://blueprints.launchpad.net/p1tr/+spec/pep8-compliance).
Code needs to be well readable that it can be maintained and improved
easier. Work on this issue has already started - and it caused
trouble.

Letting pylint run over P1tr scripts returns a nice list of lines,
where the code style could be improved. Happy programmer does the
improvements and doesn't think sufficiently about the consequences.
One little change can cause whole P1tr not be executable. Such things
happened and had to be corrected.

I think it is needless to say that if we had unit tests the whole
trouble could have been avoided, but unfortunately nobody likes
writing unit tests, although the bounty for it is the Order of the
AustrianGeekForce, first class.

What I want to say:
PEP 8 compliance is a good thing, but make sure that P1tr works after
such changes.
I already committed a broken P1tr myself, so I know about which
mistakes I'm talking about :p

Greetings,
Chris