-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
Apply PEP8 convetion to the codebase #65
Conversation
@diogoosorio I've done a bit of a tricky merge here (two PR's prior to this one) and although I can pass all manual tests, I believe I've broken the Travis CI build in a way I'm unsure of. Here's the output, any ideas?:
|
I'll give it a look within the next couple of days. Don't get offended by the remark, but as a maintainer is 100% legitimate or you to ask for the contributor to preform the rebase with master, prior to even preforming the review. You don't have to rebase everything yourself. 😄 |
No offence taken. I mostly took care of it as I already valued the contributions made. It's important I also learn more about the test cases in order to better maintain them but a bit time pressed this week. |
If the response payload doesn't contain a 'Content-Length' header and the '--ignore-content-length' parameter is provided, the script was trying to cast a None type into an integer. This commit fixes that by return '0' has the 'Content-Length' if the header isn't present.
With the codebase adhering to PEP 8, there's no longer any need to omit certain rules when validating the pep8 convention.
@codingo I've rebased it directly to master and try to kept the changes you've made in this branch (my last 2 commits). Please give it a thorough review and let me know if anything's missing. |
As discussed in #61 tihs PR makes the codebase adhere to the standards defined on PEP8.