Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #31639
| Date | 2012-10-18 15:59 +0200 |
|---|---|
| From | Jean-Michel Pichavant <jeanmichel@sequans.com> |
| Subject | Re: A desperate lunge for on-topic-ness |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2433.1350568745.27098.python-list@python.org> (permalink) |
----- Original Message ----- > On 2012-10-18, Zero Piraeus <schesis@gmail.com> wrote: > > > What are people's preferred strategies for dealing with lines that > > go > > over 79 characters? A few I can think of off the bat: > > I try to do what's easiest to read and understand. Sometimes that > means using a line thats 120 characters long, sometimes that means > breaking up the line. > Imo, def. a good approach to the problem. Mark's also pointed the fact that the guidelines themselves state that rules are made to be broken when they need to be. The 79 char limit purpose is to allow someone to read the code on a 80 char terminal (and allow old printers to print the code). If following this rules breaks readability for all other terminals, meaning 99,99% of them, you know what to do. JM
Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread
Re: A desperate lunge for on-topic-ness Jean-Michel Pichavant <jeanmichel@sequans.com> - 2012-10-18 15:59 +0200
Re: A desperate lunge for on-topic-ness Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-10-19 01:34 +0000
Re: A desperate lunge for on-topic-ness Demian Brecht <demianbrecht@gmail.com> - 2012-10-19 10:59 -0700
csiph-web