Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-advocacy-owner+archive@lists.postgresql.org>)
	id 1nr9T3-0006Iu-6Y
	for pgsql-advocacy@arkaria.postgresql.org; Wed, 18 May 2022 02:31:17 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-advocacy-owner+archive@lists.postgresql.org>)
	id 1nr9T2-00046n-3l
	for pgsql-advocacy@arkaria.postgresql.org; Wed, 18 May 2022 02:31:16 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <justin@postgresql.org>)
	id 1nr9T1-00046e-A8
	for pgsql-advocacy@lists.postgresql.org; Wed, 18 May 2022 02:31:15 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <justin@postgresql.org>)
	id 1nr9Sy-0008Ao-2u
	for pgsql-advocacy@lists.postgresql.org; Wed, 18 May 2022 02:31:14 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=postgresql.org; s=20171124; h=Message-ID:References:In-Reply-To:Subject:Cc:
	To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:
	Reply-To:Content-ID:Content-Description;
	bh=y7RMyJv4UK6EFPIjkNYxUWeK/HouVWlkTxOthgxDTck=; b=rcLpaMlfBcxgCsu5F3YhxVlrlu
	/nGQbveEvrIwEPcqr49G6xsS9aUbKm+9i5k+RIGRgNfUSu487iL+8g+5842qGQ7m09tJ+j7yITBWU
	86QVaLKTO2dMvUhxcu5+TDlwke4OzBNSnclX/GKipZFt4TxqwVbbFSqsVlSMfnfXd8KumIlPWHEUh
	/z555TA7+bvYFcFkuqgf2PXlIihm6FdGMqg/7IDqAxALyXkd65QFs3jN6WG/saPyUjx5dMMc32BuA
	u7xMp5kjbBpffZPRGFDe2UeYa6tXqZe+8qc2w38XDGxNpVCGshM+Kxo6Bp7KgMSZXauPVNj60ozxs
	0dm4iTyw==;
Received: from meldrar.postgresql.org ([87.238.57.231]
 helo=webmail.postgresql.org)
	by meldrar.postgresql.org with esmtpsa
 (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.92)
	(envelope-from <justin@postgresql.org>)
	id 1nr9Su-0003oK-8U; Wed, 18 May 2022 02:31:10 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Wed, 18 May 2022 12:31:07 +1000
From: Justin Clift <justin@postgresql.org>
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>, PostgreSQL Advocacy
 <pgsql-advocacy@lists.postgresql.org>
Subject: Re: PostgreSQL 15 Beta 1 release announcement draft
In-Reply-To: <fb35489b-79cf-deca-be7a-924316347ef7@aklaver.com>
References: <d00932de-3da6-1f9c-c3c6-8d2d084efa7c@postgresql.org>
 <fb35489b-79cf-deca-be7a-924316347ef7@aklaver.com>
Message-ID: <49bdb7dcbe4b780bf4a621a59257f94b@postgresql.org>
X-Sender: justin@postgresql.org
User-Agent: Roundcube Webmail/1.3.17
List-Id: <pgsql-advocacy.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-advocacy@lists.postgresql.org>
List-Owner: <mailto:pgsql-advocacy-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-advocacy>
Archived-At: 
 <https://www.postgresql.org/message-id/49bdb7dcbe4b780bf4a621a59257f94b%40postgresql.org>
Precedence: bulk

On 2022-05-18 10:24, Adrian Klaver wrote:
<snip>
> I think there needs to be mention that plpythonu and plpython2u  are
> going away and there will only be plpython3u . Especially since in
> current docs it says:
> 
> https://www.postgresql.org/docs/current/plpython-python23.html
> 
> "The language named plpythonu implements PL/Python based on the
> default Python language variant, which is currently Python 2. (This
> default is independent of what any local Python installations might
> consider to be their “default”, for example, what /usr/bin/python
> might be.) 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."
> 
> This is going to catch people by surprise. A heads up in the release
> announcement will mitigate that.

This sounds like a good idea. :)

+ Justin