Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsreader4.netcologne.de!news.netcologne.de!xlned.com!feeder3.xlned.com!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <ktbebp$or0$2@reader1.panix.com>
References: <51F6C5F5.5020201@Gmail.com> <CAPM-O+y++Q499zgYBGxTdPhLX9D_CfOwHnRTTo+ncQrPVFpD7g@mail.gmail.com> <mailman.5265.1375129503.3114.python-list@python.org> <51f6e1d8$0$30000$c3e8da3$5496439d@news.astraweb.com> <51F6ED13.5010508@Gmail.com> <EB2D8574-23DC-408F-B87E-A0B84B6DC7FF@leafe.com> <kt8rul$qvv$1@ger.gmane.org> <mailman.5331.1375206170.3114.python-list@python.org> <kt8ugu$jj0$1@reader1.panix.com> <CAN1F8qXS6H3dV6jZSJ_N6NTOQjrKKzy8h5uO3LZAWjsCXPmYKA@mail.gmail.com> <mailman.8.1375268124.1251.python-list@python.org> <b5sg7fFjcopU1@mid.individual.net> <ktbebp$or0$2@reader1.panix.com>
Date: Wed, 31 Jul 2013 14:45:17 -0300
Subject: Re: PEP8 79 char max
From: Marcelo MD <lists.md@gmail.com>
To: python-list@python.org
Content-Type: multipart/alternative; boundary=e89a8ffbab75ec7bd304e2d24967
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.42.1375292728.1251.python-list@python.org>
Lines: 63
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:51676

--e89a8ffbab75ec7bd304e2d24967
Content-Type: text/plain; charset=ISO-8859-1

>
> In my experience, aligning columns in large tables reduces maintence
> cost by making it much easier/faster to see what you've got and by
> providing a way to visually "prompt" you for the correct value in the
> correct place when you add new lines.
>
>
Works great until one of the values changes in size. Say:
bla = (
....1.0, 1.1, 1.2,
....2.0, 2.1, 2.2,
....3.0, 2.1, 3.2,
)

And one day you have to change '2.1' to '2.09999':
bla = (
....1.0, 1.1, 1.2,
....2.0, 2.09999, 2.2,
....3.0, 2.1, 3.2,
)

If this happens more than once ( or twice, because I'm patient =)),
maintaining the alignment becomes a chore. So I only align columns if I'm
typing a table I know won't change.


-- 
Marcelo Mallmann Dias

--e89a8ffbab75ec7bd304e2d24967
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">
<div class=3D""><div class=3D"h5"><span style=3D"color:rgb(34,34,34)">In my=
 experience, aligning columns in large tables reduces maintence</span><br><=
/div></div>
cost by making it much easier/faster to see what you&#39;ve got and by<br>
providing a way to visually &quot;prompt&quot; you for the correct value in=
 the<br>
correct place when you add new lines.<br>
<span class=3D""><font color=3D"#888888"><br></font></span></blockquote></d=
iv><div class=3D"gmail_extra" style><br>Works great until one of the values=
 changes in size. Say:<br></div><div class=3D"gmail_extra" style>bla =3D (<=
br>....1.0, 1.1, 1.2,<br>
....2.0, 2.1, 2.2,<br>....3.0, 2.1, 3.2,<br>)<br><br>And one day you have t=
o change &#39;2.1&#39; to &#39;2.09999&#39;:</div><div class=3D"gmail_extra=
" style>bla =3D (<br>....1.0, 1.1, 1.2,<br>....2.0, 2.09999, 2.2,<br>....3.=
0, 2.1, 3.2,<br>
)<br><br>If this happens more than once (=A0or twice, because I&#39;m patie=
nt =3D)), maintaining the alignment becomes a chore. So I only align column=
s if I&#39;m typing a table I know won&#39;t change.</div><br clear=3D"all"=
><div>
<br></div>-- <br>Marcelo Mallmann Dias<br>
</div></div>

--e89a8ffbab75ec7bd304e2d24967--