| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Steven Pousty <steve(dot)pousty(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Switching PL/Python to Python 3 by default in PostgreSQL 12 |
| Date: | 2019-07-06 22:28:14 |
| Message-ID: | 597f1c6c-9cda-8b9c-f401-06ebb728165a@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steven Pousty | 2019-07-06 22:34:56 | Re: Switching PL/Python to Python 3 by default in PostgreSQL 12 |
| Previous Message | Tomas Vondra | 2019-07-06 22:02:38 | Re: Multivariate MCV list vs. statistics target |