Steve Bergman schrieb:
> In my opinion, Guido's 80 character line limit hurts readability for no
> good reason. (Even old, narrow, dot matrix printers can handle 96-132
> characters/line.)
> 
> 100 character lines are what I target.  I use more when the longer
> lined form is more readable.

With a normal screensize (i.e. 1280x1024) and using an IDE it is very difficult
to have an editing window even 80 chars wide in an acceptable font size.

I hate it when I have to scroll horizontally, so I alway break lines, if they
are too long. Luckily in Python there are many ways to do this:

1) Reconition of open parenthesis

2) Backslash at line end

3) Concatenation of string literals in conjunction with 1) or 2)

Jeff Hinrichs wrote:
> One final group question, does anyone else have issues with
>   from sqlobject import *
> I didn't find a specific reference to it in PEP 8, general wisdom
> considers it bad form unless you are at the interactive prompt

I see this mainly as a readability issue. If the module has a proper
declaration of it's namespace (__all__), then there should be no suprises about
what you import (and AFAICS all TG modules have __all__).

But both forms have implications on how easy it is to read the code. If you do

from foo.bar.boo import *

and you're using names from the foo package further down in you code, the
reader cannot see, where this name was defined.

If you're using

import foo.bar.boo

...

spamm = foo.bar.boo.blub('eggs')

you will end up with many long lines, that you will have to break  etc.

(the latter form might also incur a slight speed penalty because of all the
necessary namespace lookups)

Chris

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to