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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Made the code PEP8-compliant #1476

Merged
merged 104 commits into from Jan 30, 2015

Conversation

Projects
None yet
6 participants
@aviau
Contributor

aviau commented Jan 27, 2015

So yeah. We did some PEP8 tonight. All tests pass. We have also added a PEP8 check to Travis.

//cc @Seb-Solon @gst @titilambert @Freddrickk 馃嵒 馃嵒

REBASES ARE COMING

@aviau aviau changed the title from Pylint party to Made the code PEP8-compliant Jan 27, 2015

@coveralls

This comment has been minimized.

Show comment
Hide comment
@coveralls

coveralls Jan 27, 2015

Coverage Status

Coverage remained the same at % when pulling b7133f7 on savoirfairelinux:PylintParty into 025964a on naparuba:master.

Coverage Status

Coverage remained the same at % when pulling b7133f7 on savoirfairelinux:PylintParty into 025964a on naparuba:master.

@naparuba

This comment has been minimized.

Show comment
Hide comment
@naparuba

naparuba Jan 30, 2015

Owner

Merge in progress, just a conflict and tests are running

Owner

naparuba commented Jan 30, 2015

Merge in progress, just a conflict and tests are running

@naparuba naparuba merged commit b7133f7 into naparuba:master Jan 30, 2015

1 check passed

continuous-integration/travis-ci The Travis CI build passed
Details
@naparuba

This comment has been minimized.

Show comment
Hide comment
@naparuba

naparuba Jan 30, 2015

Owner

GG all ^^

Owner

naparuba commented Jan 30, 2015

GG all ^^

@gst gst deleted the savoirfairelinux:PylintParty branch Jan 30, 2015

@aviau

This comment has been minimized.

Show comment
Hide comment
@aviau

aviau Jan 30, 2015

Contributor

@Freddrickk oops!

I opened a PR to fix: #1487

@Freddrickk oops!

I opened a PR to fix: #1487

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment