Skip to content
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

Add PEP8 check to Travis-CI #3273

Merged
merged 3 commits into from Mar 9, 2014
Merged

Add PEP8 check to Travis-CI #3273

merged 3 commits into from Mar 9, 2014

Conversation

pv
Copy link
Member

@pv pv commented Feb 2, 2014

Not sure if this is a good idea, but it should eliminate whitespace fixing commits that can cause merge conflicts.

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 120da6e on pv:pep8 into e31a4ae on scipy:master.

@@ -38,5 +38,5 @@ commands=python {toxinidir}/runtests.py -n -m full {posargs:}
[pep8]
max_line_length=79
statistics = True
ignore = E121,E122,E123,E125,E126,E127,E128,E226,E231,E501,E712
ignore = E121,E122,E123,E125,E126,E127,E128,E226,E231,E501,E712,W291,W293,W391
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why ignore all the whitespace related warnings? That passed until recently, so I suggest to keep that as is.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't find that trailing whitespace harms readability, so I don't see the point in checking for it. (The check does not pass any more.)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, it doesn't harm readability. However some editors (like Vim, which I use) automatically strip trailing whitespace, so you still get commits with diffs for lines that have nothing to do with the actual code changes in those commits. If you prefer not checking for it that's fine with me, just want to point out that there is a good reason for the check.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. However, I suspect that enforcing that is more hassle than useful.
It's probably embarrassing enough to tell people to fix their visible whitespace :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But I have vim set up to show trailing whitespace. It's always visible and ugly ;)

@rgommers
Copy link
Member

rgommers commented Feb 3, 2014

Ironically, has a merge conflict:)

@rgommers
Copy link
Member

rgommers commented Feb 3, 2014

+1 for enabling this. Will be a pain for a while, but it teaches people to set up their editor correctly.

@pv
Copy link
Member Author

pv commented Feb 3, 2014

Rebased

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling ac9d395 on pv:pep8 into f3acfe3 on scipy:master.

@pv pv added the PR label Feb 19, 2014
@rgommers
Copy link
Member

rgommers commented Mar 9, 2014

Time to merge this?

@pv
Copy link
Member Author

pv commented Mar 9, 2014

Rebased once again. I don't see blockers for merging.

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling d217da1 on pv:pep8 into 473dca9 on scipy:master.

rgommers added a commit that referenced this pull request Mar 9, 2014
Add PEP8 check to Travis-CI
@rgommers rgommers merged commit 10bdec2 into scipy:master Mar 9, 2014
@rgommers
Copy link
Member

rgommers commented Mar 9, 2014

OK in it goes. Thanks @pv.

@rgommers rgommers added this to the 0.15.0 milestone Mar 9, 2014
@cowlicks
Copy link
Contributor

Any reason not to do pep8 and pyflakes on the same worker?

@rgommers
Copy link
Member

Not really

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task A straightforward change, verification or fix.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants