git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Giokas <1007380@gmail.com>
To: git@vger.kernel.org
Subject: Re: Conforming to pep8
Date: Fri, 9 May 2014 00:16:23 -0500	[thread overview]
Message-ID: <20140509051623.GB9051@wst420> (raw)
In-Reply-To: <536c5b4d9e2c9_377dfcb2f02b@nysa.notmuch>

[-- Attachment #1: Type: text/plain, Size: 2510 bytes --]

On Thu, May 08, 2014 at 11:36:29PM -0500, Felipe Contreras wrote:
> William Giokas wrote:
> > E401: Multi-line imports seems like something that would just be
> > changing one line
> 
> Yes, and make the code very annoying.

It's 1 extra line in git-remote-hg, and 4 lines in git-remote-bzr. I'll
even send in patches for the current version you have in your tree if
you'd like. It would make testing removal of an import easier, and the
adding of imports would be consistent. They can still be grouped, but
having them on a single line kind of limits the ease of manipulation for
testing and possible packager patching if needed.

> > E302: Blank lines don't seem to be that hard to do either. That can even
> > be automated quite reliably. It shouldn't detract from the readability,
> > juts makes the file a bit longer.
> 
> The problem is not that it's hard to do, the problem is that it makes
> the code uglier.

I would disagree, but this is one of the less important things.

> > E20{1,2,3}: Extra whitespace is something that just makes things more
> > consistent and readable.
> 
> I don't see how this:
> 
>   {'100755': 'x', '120000': 'l'}
> 
> Is more readable than this:
> 
>   { '100755': 'x', '120000': 'l' }
> 
> No strong opinion on this one though.

It's not so much that it's wrong or less readable, but there is
inconsistency on this one and I'd err pep8. Again, will send a patch to
your tree for you to review, though it looks like you mostly fixed this
in [1].

> 
> > E12{6,8}: continuation line indenting is another thing that helps
> > consistency.
> 
> I don't see how.
> 



> > >   max-line-length = 160
> > 
> > The standard states that this should, at most, be increased to a value
> > between 80 and 100.
> 
> And why's that?
> 
> This has been discussed many times in the LKML, and the end result is
> that we don't live in the 60's, our terminals are not constrained to 60
> characters. Going beyond 100 is fine.

Fair enough. At the same time, it'd only change 14 lines in the current
git.git tree and would probably increase the readability of some of the
sections. I noticed that some of the changes in the referenced patch
actually fixed this on a few lines as well.

[1]: https://github.com/felipec/git/commit/12374c0e09a84945a202bb5ba7981a223d233d0b

Thanks,
-- 
William Giokas | KaiSforza | http://kaictl.net/
GnuPG Key: 0x73CD09CF
Fingerprint: F73F 50EF BBE2 9846 8306  E6B8 6902 06D8 73CD 09CF

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-05-09  5:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09  1:54 Conforming to pep8 William Giokas
2014-05-09  2:09 ` Jonathan Nieder
2014-05-09 14:33   ` Michael Haggerty
2014-05-09  2:10 ` Felipe Contreras
2014-05-09  3:57   ` William Giokas
2014-05-09  4:36     ` Felipe Contreras
2014-05-09  5:16       ` William Giokas [this message]
2014-05-09  7:18         ` Felipe Contreras
2014-05-09  7:28           ` William Giokas
2014-05-09  7:35             ` Felipe Contreras
2014-05-09  7:44               ` William Giokas
2014-05-09 16:01                 ` W. Trevor King
2014-05-09 16:14                   ` Felipe Contreras
2014-05-09  8:05 ` John Keeping

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140509051623.GB9051@wst420 \
    --to=1007380@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).