On tis, 2010-07-06 at 18:15 -0400, Tom Lane wrote:
> At this point it seems clear to me that we've not adequately thought
> through the implications of having two python versions in one
> application namespace, and I'm not sure the Python people have either.
> I think we need to do something to block that from happening, at least
> until we have a plausible way to make it work.

How about this?

In response to

• Re: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will at 2010-07-06 22:15:29 from Tom Lane

Responses

• Re: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will at 2010-07-07 21:31:52 from Tom Lane

pgsql-hackers by date

Next:	From: Josh Berkus	Date: 2010-07-07 21:14:06
	Subject: Re: Why is vacuum_defer_cleanup_age PGC_USERSET?
Previous:	From: Robert Haas	Date: 2010-07-07 20:44:10
	Subject: Re: t_self as system column

pgsql-committers by date

Next:	From: Tom Lane	Date: 2010-07-07 21:31:52
	Subject: Re: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will
Previous:	From: Tom Lane	Date: 2010-07-07 15:13:21
	Subject: pgsql: Adjust mbutils.c so it won't get broken by future pgindent runs.