Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.albasani.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed1a.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: <dcd72881-7ee2-4bc3-90ab-7912b4bea05b@googlegroups.com>
References: <9daf0806-02de-4447-964c-c8f8953c23e5@googlegroups.com> <10101874-2995-4acd-9851-989603f052e3@googlegroups.com> <bd158c7b-5511-472c-bce3-cc7b6b7747f6@googlegroups.com> <e2b2b9d5-56bd-4455-b8c3-205000d9acb3@googlegroups.com> <mailman.8369.1395437459.18130.python-list@python.org> <a0403642-c384-4623-bbfd-77c48285ec96@googlegroups.com> <mailman.8377.1395456097.18130.python-list@python.org> <dcd72881-7ee2-4bc3-90ab-7912b4bea05b@googlegroups.com>
Date: Sat, 22 Mar 2014 15:51:13 +1100
Subject: Re: Explanation of this Python language feature? [x for x in x for x in x] (to flatten a nested list)
From: Chris Angelico <rosuav@gmail.com>
Cc: "python-list@python.org" <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.8382.1395463877.18130.python-list@python.org>
Lines: 39
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:68745

On Sat, Mar 22, 2014 at 3:39 PM, Rustom Mody <rustompmody@gmail.com> wrote:
>> So if that's not going to be broken, how is this fundamentally different?
>
>> def func_loop():
>>     for x in 1,2,3:
>>         yield (lambda: x)
>
> Thats using a for-loop
> A 'for' in a comprehension carries a different intention, the matching names
> being merely coincidental.

So what you're saying is that these two are fundamentally different:

def unrolled():
    x = 1
    yield (lambda: x)
    x = 2
    yield (lambda: x)
    x = 3
    yield (lambda: x)

def loop():
    for x in 1,2,3:
        yield (lambda: x)

In other words, a loop should be implemented as a separate binding
each time, not a rebinding. That's an interesting point, and it does
make some sense; effectively, what you want is for the body of a for
loop to be a new scope, a unique scope every iteration of the loop,
and one that automatically closes over all variables in the parent
scope (including for assignments) except for the loop
iteration/counter variable.

That does make some sense, but it doesn't really fit Python's concept.
It would, however, fit a more C-like language, where locals are
declared (in Python, you'd have to put a whole lot of implicit
'nonlocal' statements at the top of the loop).

ChrisAg