MIME-Version: 1.0
In-Reply-To: <CALwzid=oS6H-ETtTPsRPawas-Gkj=7hkTWcwLmE8vZ7NdR5R+g@mail.gmail.com>
References: <9a0c67be-de3a-4770-bf06-e158783bfff0@googlegroups.com> <mailman.14869.1413339808.18130.python-list@python.org> <m1l7l8$sce$1@dont-email.me> <CAMw+j7+CisEW8=jyVyxkj_7FDj_Lmj+CjjNbJ3Coi2c2q3C2Gg@mail.gmail.com> <m1m9ut$v8f$1@ger.gmane.org> <mailman.14893.1413401464.18130.python-list@python.org> <b474caf0-d910-4f59-86d8-006d316e858b@googlegroups.com> <54424691$0$12978$c3e8da3$5496439d@news.astraweb.com> <bd24df51-bdee-4ccc-82f7-28bf6dbd8bf5@googlegroups.com> <CALwzid=oS6H-ETtTPsRPawas-Gkj=7hkTWcwLmE8vZ7NdR5R+g@mail.gmail.com>
From: Ian Kelly <ian.g.kelly@gmail.com>
Date: Mon, 20 Oct 2014 11:57:44 -0600
Subject: Re: Is there an easy way to control indents in Python
To: Python <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.14999.1413827908.18130.python-list@python.org>
Lines: 53
NNTP-Posting-Host: 2001:888:2000:d::a6
Path: csiph.com!usenet.pasdenom.info!bete-des-vosges.org!feed.ac-versailles.fr!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Xref: csiph.com comp.lang.python:79319

On Mon, Oct 20, 2014 at 11:54 AM, Ian Kelly <ian.g.kelly@gmail.com> wrote:
> On Mon, Oct 20, 2014 at 9:54 AM, Simon Kennedy <sffjunkie@gmail.com> wrot=
e:
>> Not having ever attempted to go beyond even the basics of Perl, the aspe=
ct that causes me to refer to Perl 'dismissively' as well comment in this t=
hread, is that I don't find Perl to be an aesthetically pleasing language a=
nd I consider Python functions which have no blank lines in them to be a sm=
all step towards Perl.
>>
>> Some people do not like Python's indentation rules but for me it's a lar=
ge part of what draws me to program in Python. Spaces for indentation and b=
lank lines are both aspects of how I like to program.
>>
>> I write in Python because I like to, not because I have to.
>>
>> I think the only reason I might code a function with no blank lines was =
if I was programming in a language that using blank lines caused it to run =
too slowly.
>
> So to be clear, I'm not talking about taking a function like this
> (contrived) example and just removing the blank line:
>
> def find_path(graphdata, start, end):
>     edges =3D map(str.split, lines)
>     graph =3D collections.defaultdict(list)
>     for node1, node2, weight in edges:
>         graph[node1].append((node[2], int(weight)))
>         graph[node2].append((node[1], int(weight)))
>
>     open_heap =3D [(0, (start,))]
>     closed_set =3D set()
>     while open_heap:
>         cost, path =3D heapq.heappop(open_heap)
>         current_node =3D path[-1]
>         if current_node =3D=3D end:
>             return path
>         if current_node in closed_set:
>             continue
>         for next_node, weight in graph[current_node]:
>             heapq.heappush((cost + weight, path + (next_node,)))
>         closed_set.add(current_node)
>     else:
>         raise ValueError("No path from start to end")
>
> Rather, I'm saying that where the blank line is should be the start of
> a new function. There would still be a blank line, just no longer
> inside the function.
>
> Now, maybe you think there should be more blank lines in the above, in
> which case we'll just have to disagree on that point.

By the way, I didn't test that at all, which is why I've spotted at
least two bugs in it since sending the message.