Auto PEP8 #18
Auto PEP8 #18
Conversation
Ran autopep8 against codebase. Not tested. https://pypi.python.org/pypi/autopep8
|
you're going to have your name all over his code if this gets in, heh |
|
^ this will also conflict with my pull request, so whichever one merges in first, the second will have to re-merge master and fix the conflicts |
|
If there is a choice I would say have your changes go in first. Despite the line number counts this doesn't represent a whole lot of time on my part. |
Some hands on cleaning. Mostly refactoring comments and string constants
|
hm, if you check issues, there's an issue opened for pep8 2 years ago. i think this isn't going to get merged any time soon. non-pep8 code is so difficult to work with. i'm going to fork this for my own needs for now, as i have a lot more changes in mind |
|
The first commit, 34a4d1a, pushes lines beyond 80 characters. The latter appears to rectify the issue. I'll inspect locally and verify everything is kosher before merging. |
…t2 as a test requirement for Python <= 2.6. Fixed a bug in Path.add() where in some cases the absoluteness of the Path wasn't preserved.
|
Code now formatted to PEP8: commit 6df53fa + a manual review and tweaks. Thank you for bringing this issue to my attention and for your pull requests, slick666 and Andrew. |
Ran autopep8 against codebase. Not tested.
https://pypi.python.org/pypi/autopep8