Pep 8/257 about pico-python HOT 3 CLOSED

re: 80-char limit:
I also used to stick with 80-char limits, although with higher resolution screens I really don't think it makes sense. When you had 1024x768 sure you don't want to be scrolling much. The 80-char limit came from ancient terminals, and people seem to have stuck to it with all sorts of newer systems. I'm all for some reasonable limit to make diff viewing easier, but I think 80 is too short. There's a good point at http://lkml.org/lkml/2009/12/17/229 too - if you break lines up, it makes it harder to search for something. e.g. if you break a string up because it's longer than 80 chars, you can't search for part of that string now since it's split.

re: alignment:
IMHO readability is king... especially with a project like ours, I can't imagine we'll be modifying things a lot once they've matured a bit. Whilst it will result in some extra commit noise, I'd rather it's easier for the many users after who will be reading it, rather than the handful doing development work.

My vote is screw PEP8, or at least the portions that seem somewhat counter-intuitive.

from pico-python.

80 char limit.

I think 80 char limit especially doesn't make sense python with tabs = 4 spaces.
you already lose 10% because class, def, inside an if statement in a while loop, you have lost 20%....

maybe 100 or 120? I've never actually enforced a limit, but I think it might be a good idea.

Alignment:
Ok. I'll keep alignment that makes visual sense.

from pico-python.

You can ignore some whitespace changes with this:

http://stackoverflow.com/questions/4449834/commit-without-whitespace-changes-on-github

from pico-python.