Re: PL/Python result set slicing broken in Python 3

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: PL/Python result set slicing broken in Python 3
Дата
Msg-id CA+TgmoZvCRtsWRqR69cF4QfLfD_=Fj1-gRfk-HMRZGbhWWYLNw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: PL/Python result set slicing broken in Python 3  (Jan Urbański <wulczer@wulczer.org>)
Ответы Re: PL/Python result set slicing broken in Python 3  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-hackers
On Sat, May 5, 2012 at 4:45 PM, Jan Urbański <wulczer@wulczer.org> wrote:
>> I found some instructions on how to deal with the Python 2/Python 3
>> slicing mess:
>>
>>
>> http://renesd.blogspot.com/2009/07/python3-c-api-simple-slicing-sqslice.html
>
>
> Thanks to the helpful folk at #python I found out that the fix is much
> easier. Attached is a patch that fixes the bug and passes regression tests
> on Pythons 2.3 through 3.2.
>
> 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).
>
> Do we want to backpatch this? If so, I'd need to produce a version that
> applies to the monolithic plpython.c file from the previous releases.

Did this get forgotten about?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: Gsoc2012 idea, tablesample
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Draft release notes complete