Where are we on Python 2.5?

---------------------------------------------------------------------------

Tom Lane wrote:
> Neil Conway <neilc(at)samurai(dot)com> writes:
> >> No, it just looks like a Python API 2.5 change to me
> 
> > Attached is a patch that fixes the warnings. Unfortunately, it seems
> > this patch won't compile against Python 2.4: the 2.5 API requires the
> > use of some typedef's that AFAICS were only introduced in 2.5.
> 
> > Since we presumably still want to support Python < 2.5, we can either
> > not apply this patch and tolerate the warnings, or else we can
> > workaround the incompatibility with some preprecessor hackery (e.g.
> > supply the missing typedef's ourselves if Python doesn't provide them).
> 
> Sounds like #ifdef time to me --- but it seems a bit strange; wouldn't
> the Python guys have taken a bit more care for compatibility of
> user-supplied code?  We're hardly the only people who want to support
> multiple Python versions.  Perhaps they provide a compatibility hack
> that you didn't spot?
> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
> 
>                http://archives.postgresql.org

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

• Re: PL/Python warnings in CVS HEAD at 2007-03-06 05:18:42 from Tom Lane

Responses

• Re: PL/Python warnings in CVS HEAD at 2007-04-03 08:56:16 from Marko Kreen

pgsql-hackers by date

Next:	From: Bruce Momjian	Date: 2007-04-02 23:06:11
	Subject: Re: CREATE TABLE LIKE INCLUDING INDEXES support
Previous:	From: Bruce Momjian	Date: 2007-04-02 22:57:44
	Subject: Re: Re: [HACKERS] [COMMITTERS] pgsql: Add GUC temp_tablespaces to provide a default location for