Skip to content

Flake8 cleanup workflows/anatomical #350

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Feb 10, 2017
Merged

Flake8 cleanup workflows/anatomical #350

merged 4 commits into from
Feb 10, 2017

Conversation

effigies
Copy link
Member

Mostly line length and block spacing issues. These keep popping up when I style check before committing in #347, but I don't really want to infect that PR with these cleanups.

If people don't like these changes, can we put in a tox.ini or something to tell flake8 what style issues to report?

@rwblair
Copy link
Contributor

rwblair commented Jan 30, 2017

LGTM. Maybe we bump minimum line length? I know its against the holy scripture for public code... Pylint only complains at 100 characters. But it also has some interesting ideas about what good looking code is that are not in pep8.

@oesteban
Copy link
Member

I'm totally open to whatever standard you guys want to stick with. My only issue is that 79 characters is quite reduced, I would advocate for 99.

@effigies effigies force-pushed the pep8 branch 2 times, most recently from fae9a05 to 6e760d9 Compare January 31, 2017 02:15
@effigies
Copy link
Member Author

99 works. Added a tox.ini, and ran through the rest of the workflows directory to get a sense of how much changes.

Mostly finding some blank line counts and unused imports. A few undefined names, which I left alone, not knowing what they were supposed to be.

@oesteban
Copy link
Member

Is this ready to merge?

@effigies
Copy link
Member Author

effigies commented Feb 10, 2017 via email

@oesteban oesteban merged commit 18d3c70 into nipreps:master Feb 10, 2017
@effigies effigies deleted the pep8 branch February 14, 2017 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants