On Tue, Mar 24, 2009 at 12:15:17AM -0700, Christopher Lee wrote: -> Titus, regarding PEP 8, I have to confess I had forgotten that it -> calls for a blank line after every method. Especially for methods -> that are only a few lines, I tended not to do that, because I thought -> the indentation showed the method boundaries clearly, and I like to be -> able to see as much of a class "at a glance" (i.e. in a window) as -> possible, to see how all the methods work together. But we can add -> the extra blank lines if people feel this improves readability.
Yes, and in fact you convinced me that blank lines were ixnay, too, a while back ;). When I went back and re-read PEP8 before looking at seqdb, I noticed that blank lines were mandated. I could go either way, but I would default to PEP 8 unless you have a strong opinion. I think it's nice to have a Python-wide coding standard as part of the language, and it will simplify discussions with new developers. --titus -- C. Titus Brown, c...@msu.edu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
