Re: Switching PL/Python to Python 3 by default in PostgreSQL 12

Поиск
Список
Период
Сортировка
От Steven Pousty
Тема Re: Switching PL/Python to Python 3 by default in PostgreSQL 12
Дата
Msg-id CAKmB1PF+otdHHsAJNK6_mOP7WhSSXBFUX4S-0MqMaTxbRcDcgA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Switching PL/Python to Python 3 by default in PostgreSQL 12  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: Switching PL/Python to Python 3 by default in PostgreSQL 12  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
Why would it be a 13 or later issue?
I am specifically talking about changing the default. 

On Sat, Jul 6, 2019, 6:28 PM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
On 2019-07-06 21:02, Steven Pousty wrote:
> /" The default will probably be changed to Python 3 in a distant future
> release of PostgreSQL, depending on the progress of the migration to
> Python 3 in the Python community."/
>
> I know we are late in the Postgresql 12 cycle but I think switching the
> default to Python 3 is warranted given:

"The default" in the above statement refers to what version the language
name "plpythonu" invokes.  That is separate from whether an installer or
packager chooses to install a Python-2-based version.  I expect that as
operating systems remove Python 2 from their systems, packagers will
also remove Python-2-based plpython packages.  So there is no issue.

We could change plpythonu to be an alias for plpython3u instead of
plpython2u, but that would be a PG13 (or later) change.  I notice that
PEP-394 now supports this.

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Switching PL/Python to Python 3 by default in PostgreSQL 12
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.