[Python-Dev] Informal educator feedback on PEP 572 (was Re: 2018 Python Language Summit coverage, last part)

Guido van Rossum guido at python.org
Sun Jun 24 19:28:16 EDT 2018

On Sun, Jun 24, 2018 at 2:10 PM Chris Angelico <rosuav at gmail.com> wrote:

> On Mon, Jun 25, 2018 at 4:06 AM, Steven D'Aprano <steve at pearwood.info>
> wrote:
> >
> > Remember, the driving use-case which started this (ever-so-long)
> > discussion was the ability to push data into a comprehension and then
> > update it on each iteration, something like this:
> >
> >     x = initial_value()
> >     results = [x := transform(x, i) for i in sequence]
> Which means there is another option.
> 5. Have the assignment be local to the comprehension, but the initial
> value of ANY variable is looked up from the surrounding scopes.
> That is: you will NEVER get UnboundLocalError from a
> comprehension/genexp; instead, you will look up the name as if it were
> in the surrounding scope, either getting a value or bombing with
> regular old NameError.
> Or possibly variations on this such as "the immediately surrounding
> scope only", rather than full name lookups. It'd have an awkward
> boundary somewhere, whichever way you do it.
> This isn't able to send information *out* of a comprehension, but it
> is able to send information *in*.

But this "horrifies" me for a slightly different reason: it effectively
introduces a new case of dynamic scoping, which Python used to do
everywhere but has long switched away from, with the exception of class
scopes (whose difference with function scopes sometimes confuses people --
usually people who put too much code in their class scope).

--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20180624/3bc0e2bb/attachment.html>

More information about the Python-Dev mailing list