Re: PL/Python result set slicing broken in Python 3 - Mailing list pgsql-hackers

From Jan Urbański
Subject Re: PL/Python result set slicing broken in Python 3
Date
Msg-id 4FA24A26.5000207@wulczer.org
Whole thread Raw
In response to PL/Python result set slicing broken in Python 3  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: PL/Python result set slicing broken in Python 3
List pgsql-hackers
On 02/05/12 20:18, Peter Eisentraut wrote:
> This doesn't work anymore with Python 3:
>
> rv = plpy.execute(...)
> do_something(rv[0:1])
>
> Apparently, they changed the C API for doing slicing, or rather made one
> of the two APIs for it silently do nothing.  Details are difficult to
> find, but this email message seems to contain something:
> <http://mail.python.org/pipermail/python-3000/2007-August/009851.html>.
>
> I'll try to sort this out sometime, but if someone wants to take a shot
> at it, go ahead.

Sounds ugly. I'll take a look.

Cheers,
Jan


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Advisory locks seem rather broken
Next
From: Simon Riggs
Date:
Subject: Re: Temporary tables under hot standby