PEP8 compliance about wiki HOT 7 CLOSED

I noticed that we don't have many outstanding branches. This is as good a time as any to do a PEP8 push.

What do you guys think?

from wiki.

sounds good to me. :)

from wiki.

I'll start work on a pep8 branch of app.py. I'll keep it up to date with any changes you put in alexex/master.

Any branches still open after you merge the pep8 branch will be a battle for another day.

from wiki.

@walkerh what are you using. I use SublimeText with Flake8Lint plugin that I used with an old, old commit and was able to hit PEP8, pyflask, and mccabe compliance in ~hour. Just a thought, if it helps.

from wiki.

I use plain old TextMate with the built-in pep8 script and a tool called rerun. The rerun tool lets me see the output of pep8 (or whatever build/test command I want) every time I do a "Save" in my editor.

rerun coupled with an editor that can shell out its functionality effectively turns Unix into my IDE. For larger tasks, I will create a local file (not tracked by version control) called "view.sh". I will place that script in my working tree have rerun track my working tree, ignoring any "build", "target", or "output" directories. Then whenever I change anything in either my sources or my view.sh script, rerun executes view.sh. That way I can taylor view.sh to my concerns of the moment. Typically view.sh will first run pep8, followed by fast tests, followed by cat-ing any files generated by the fasts tests, followed by slow tests with any output going to a file or pipe. I then have two terminal windows behind my editor, one showing fast response, the other slow response.

As far as the scope of the work, I'm not worried. This looks pretty small. I was holding off until most of the feature branches were merged and I had buy-in from the local community.

Now that my work day is over, I can get to work...

from wiki.

Deed is done. Went very fast. See #24.

from wiki.

With @alexex having merged #24, this issue is now closed.

from wiki.