From: | Jan Urbański <wulczer(at)wulczer(dot)org> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PL/Python result set slicing broken in Python 3 |
Date: | 2012-05-11 09:28:31 |
Message-ID: | 4FACDBBF.4010005@wulczer.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/05/12 19:45, Peter Eisentraut wrote:
> On lör, 2012-05-05 at 22:45 +0200, Jan Urbański wrote:
>> Apparently once you implement PyMappingMethods.mp_subscript you can
>> drop PySequenceMethods.sq_slice, but I guess there's no harm in
>> keeping it (and I'm not sure it'd work on Python 2.3 with only
>> mp_subscript implemented).
>
> Committed this now.
>
> From test coverage reports, I now see that PLy_result_ass_item() is no
> longer called. That's probably OK, if assignments are now handled
> through the mapping methods. But should we remove the function then?
Have you tried on Python 2.3 as well? People on #python said that if you
implement the mapping functions, the sequence slicing functions are no
longer used, but maybe we should revisit for the next release, rather
than risk introducing a regression for the benefit of removing a few
dead lines.
Cheers,
Jan
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2012-05-11 09:32:04 | Re: Draft release notes complete |
Previous Message | Peter Eisentraut | 2012-05-11 07:55:11 | Re: Draft release notes complete |