Groups > comp.lang.python > #81911

Re: PyEval_GetLocals and unreferenced variables

References	<mailman.70.1417604405.15533.python-list@python.org> <mailman.16527.1417605559.18130.python-list@python.org> <ce8dv5Fm877U1@mid.individual.net>
From	Ian Kelly <ian.g.kelly@gmail.com>
Date	2014-12-04 08:42 -0700
Subject	Re: PyEval_GetLocals and unreferenced variables
Newsgroups	comp.lang.python
Message-ID	<mailman.16561.1417707778.18130.python-list@python.org> (permalink)

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Wed, Dec 3, 2014 at 5:28 AM, Gregory Ewing <greg.ewing@canterbury.ac.nz>
wrote:
>
> Kasper Peeters wrote:
>>
>> That may have been the design plan, but in Python 2.7.6, I definitely
>> am able to inject locals via PyEval_GetLocals() and have them be visible
>> both from the C and Python side;
>
> What seems to be happening is that the dict created by
> PyEval_GetLocals() is kept around, so you can change it
> and have the changes be visible through locals() in
> Python.

That the dict is cached is an implementation detail. It's not advisable to
rely upon this, and as stated in the Python docs, the locals dict should
not be modified.

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: PyEval_GetLocals and unreferenced variables Kasper Peeters <kasper@phi-sci.com> - 2014-12-03 11:18 +0000
  Re: PyEval_GetLocals and unreferenced variables Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-12-04 01:28 +1300
    Re: PyEval_GetLocals and unreferenced variables Ian Kelly <ian.g.kelly@gmail.com> - 2014-12-04 08:42 -0700

csiph-web