Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=fCluoKIQ0/5dvrClb6wSWBY1Q5S68EnZE/07455OQBxuKTdkB5jraKmSX2xZIJcAXG ER0pxGEi4WJDByGS065IXehqXWWhbAK42Bj37buZnknZcFhJuWBf/ULwnYgDd8u3GbdB fkypoDOb5Z+XMh0uO8oUAUOtmjcHdMWn6Yotg=
MIME-Version: 1.0
In-Reply-To: <isa62l$5uu$1@r03.glglgl.eu>
References: <Fa0Fp.18193$pi2.16608@newsfe11.iad> <mailman.2325.1306861916.9059.python-list@python.org> <x2cFp.1746$QL2.985@newsfe04.iad> <mailman.2343.1306883665.9059.python-list@python.org> <crfFp.19078$pi2.10707@newsfe11.iad> <mailman.2374.1306948289.9059.python-list@python.org> <2_AFp.30000$241.24052@newsfe07.iad> <4de71c42$0$29983$c3e8da3$5496439d@news.astraweb.com> <87zkm0qyze.fsf@dpt-info.u-strasbg.fr> <94qlhsFkriU1@mid.individual.net> <isa62l$5uu$1@r03.glglgl.eu>
From: Ian Kelly <ian.g.kelly@gmail.com>
Date: Fri, 3 Jun 2011 11:53:05 -0600
Subject: Re: Something is rotten in Denmark...
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.2436.1307123618.9059.python-list@python.org>
Lines: 67
NNTP-Posting-Host: 82.94.164.166
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:6958

On Fri, Jun 3, 2011 at 2:30 AM, Thomas Rachel
<nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de>
wrote:
> So there should be a way to replace the closure of a function with a
> snapshot of it at a certain time. If there was an internal function with
> access to the readonly attribute func_closure and with the capability of
> changing or creating a cell object and thus hbeing capable of doing so, i=
t
> could be used a a decorator for a function to be "closure-snapshotted".
>
> So in
>
> funcs=3D[]
> for i in range(100):
> =A0@closure_snapshot
> =A0def f(): return i
> =A0funcs.append(f)
>
> each f's closure content cells would just be changed not to point to the
> given variables, but to a cell referenced nowhere else and initialized wi=
th
> the reference pointed to by the original cells at the given time.

For CPython 3.2:

import functools
import types

def makecell(value):
    def f():
        return value
    return f.__closure__[0]

def closure_snapshot(f):
    if f.__closure__:
        snapshot =3D tuple(makecell(cell.cell_contents) for cell in f.__clo=
sure__)
    else:
        snapshot =3D f.__closure__
    g =3D types.FunctionType(f.__code__, f.__globals__.copy(), f.__name__,
                           f.__defaults__, snapshot)
    functools.update_wrapper(g, f, functools.WRAPPER_ASSIGNMENTS +
                                ('__kwdefaults__',))
    return g

>>> funcs =3D []
>>> for i in range(10):
...   @closure_snapshot
...   def f(): return i
...   funcs.append(f)
...
>>> [f() for f in funcs]
[0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
>>> funcs =3D [closure_snapshot(lambda: i) for i in range(10)]
>>> [f() for f in funcs]
[0, 1, 2, 3, 4, 5, 6, 7, 8, 9]


It doesn't really seem any more straightforward to me than the "i=3Di"
trick.  Also, I don't know how portable this is to different Python
implementations or future versions.  Finally, note that in order to
make this work correctly in all cases (such as the first example
above, where i is a global, not a cell) we have to snapshot the
globals as well, which could cause further confusion.

Cheers,
Ian