From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | James Pye <lists(at)jwp(dot)name> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Python 3.1 support |
Date: | 2009-11-20 08:26:45 |
Message-ID: | 1258705605.28720.5.camel@fsopti579.F-Secure.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On fre, 2009-11-20 at 01:20 -0700, James Pye wrote:
> On Nov 20, 2009, at 12:02 AM, Peter Eisentraut wrote:
> > Is there any precedent for the sort of behavior that you are
> > implementing, that is, automatic sharing of variables between
> > independent executions of the same source container?
>
> import foo
>
> # bar is a regular, def'd function.
> foo.bar()
>
> ...
>
> # even in another thread, doesn't matter..
> foo.bar()
>
>
> In either call, foo.bar()'s globals() is the same dictionary object(the foo module's dictionary).
That's not what I meant, because this is the same execution of the same
source container, with threads explicitly started somewhere. You could
do the same in a plpython function (in theory, at least).
What I mean is more like, you execute the same source file twice in a
row, and the global variables are saved for the second run.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-11-20 08:30:07 | Re: enable-thread-safety defaults? |
Previous Message | James Pye | 2009-11-20 08:20:04 | Re: Python 3.1 support |