-
Notifications
You must be signed in to change notification settings - Fork 432
PEP8-conformity #137
Comments
It might be related to keeping the lines to 80 characters, which would cause more wrapping with 4 characters. Certainly a disruptive change that should not be done lightly or not while there was a lot of work in progress. |
There is a very simple reason, the Google internal style guide. Though looking at the current style guide, maybe Google has moved back to using 4 spaces internally? (I left in 2013.) |
@dhermes is right -- this code was originally written to (mostly) follow the internal google python style guide. it's still 2 spaces. i think everyone would be amenable to switching to full pep8, but as @anthmgoogle points out we'd cause a lot of churn for outstanding PRs. @nathanielmanistaatgoogle might be able to pick a good point to decree "we heretofore will use pep8". |
We did this in After that I had to use a custom script to indent the docstrings. From there, getting |
I'm not opposed to it, but spell out the benefit of switching? |
external users don't see our code and think "why does this all look funny"? |
@nathanielmanistaatgoogle WDYT about doing this? |
I think very highly of it happening. You've made most of the changes in the recent past and would be in the best position to judge the right time to do it. I'm personally sweet on pyformat and hope it is up to the task. |
@nathanielmanistaatgoogle Looking at https://github.com/google/oauth2client/pulls I think now is as good a time as any to make this happen. How do we want to usher it in? |
Run autopep8 and see how it looks? Run pyformat and see how it looks? Decide which one you like more? Decide which one you trust more? Have you any experience with either tool? "Manually" is the last manner in which I would like to usher in such a change. |
I've been down this road once before: googleapis/google-cloud-python#179 |
Here I go... |
Is there any reason why oauth2client is using two spaces for indentation instead of four, as recommended by PEP 8?
Would people be opposed to switching to PEP8-friendly code?
The text was updated successfully, but these errors were encountered: