PEP8 conformity

[ktritz]

Hey guys, I've been trying to stay mostly consistent with the PEP8 style guide. Spyder can help if you go into (on the PC): Tools->Preferences->Editor->Code Introspection/Analysis and check the box labeled 'style analysis (pep8).

This will bring up little warning icons in the left hand margin of the editor as well as small yellow marks in the scrolling region that shows non-compliant lines throughout the document.

Mostly it's going to be things like exceeding the 79 character margin, argument spacing, and indentation styles.

It would be a good idea to try to write our code consistent with the style guide as much as possible.

[drsmith48]

There are 3 packages in the anaconda distribution that check for PEP8 conformance. We can implement one of them in the testing framework. Good idea?

-Dave

David R. Smith
University of Wisconsin-Madison
(609) 243-3514

On Dec 7, 2015, at 11:41 AM, ktritz notifications@github.com wrote:

Hey guys, I've been trying to stay mostly consistent with the PEP8 style guide. Spyder can help if you go into (on the PC): Tools->Preferences->Editor->Code Introspection/Analysis and check the box labeled 'style analysis (pep8).

This will bring up little warning icons in the left hand margin of the editor as well as small yellow marks in the scrolling region that shows non-compliant lines throughout the document.

Mostly it's going to be things like exceeding the 79 character margin, argument spacing, and indentation styles.

It would be a good idea to try to write our code consistent with the style guide as much as possible.

�
Reply to this email directly or view it on GitHub.

[ktritz]

Potentially, we'll see how difficult it is to maintain PEP8 style.