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

In response to

• PL/Python result set slicing broken in Python 3 at 2012-05-02 18:18:23 from Peter Eisentraut

Responses

• Re: PL/Python result set slicing broken in Python 3 at 2012-05-04 18:00:55 from Jan Urbański

pgsql-hackers by date

Next:	From: Simon Riggs	Date: 2012-05-03 09:11:56
	Subject: Re: Temporary tables under hot standby
Previous:	From: Simon Riggs	Date: 2012-05-03 08:43:57
	Subject: Re: Advisory locks seem rather broken