From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 24336A0542; Thu, 13 Feb 2020 17:44:40 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 701501C0B5; Thu, 13 Feb 2020 17:44:39 +0100 (CET) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 24E491C0B4 for ; Thu, 13 Feb 2020 17:44:37 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Feb 2020 08:44:36 -0800 X-IronPort-AV: E=Sophos;i="5.70,437,1574150400"; d="scan'208";a="227288046" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.79]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Feb 2020 08:44:34 -0800 Date: Thu, 13 Feb 2020 16:44:31 +0000 From: Bruce Richardson To: Robin Jarry Cc: Kevin Traynor , dev@dpdk.org, Timothy Redaelli Message-ID: <20200213164431.GC845@bricha3-MOBL.ger.corp.intel.com> References: <20200212134156.jwtbsdkkt4joyu7g@6wind.com> <20200212143650.GA834@bricha3-MOBL.ger.corp.intel.com> <20200213082548.2ubko53eldaaajsl@6wind.com> <20200213102853.bndvl34wmszusmsi@6wind.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200213102853.bndvl34wmszusmsi@6wind.com> User-Agent: Mutt/1.12.1 (2019-06-15) Subject: Re: [dpdk-dev] Dropping python 2 support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Feb 13, 2020 at 11:28:53AM +0100, Robin Jarry wrote: > 2020-02-13, Kevin Traynor: > > That is true for the distribution versions, but there may be developers > > doing some compiling themselves using latest. > > > > I think it would be ok to start the process of removing python2 from > > DPDK...but...there probably needs to be some deprecation notice and time > > to allow people upgrade or raise any concerns. > > We could insert DeprecationWarnings in the python scripts when executed > with python2 but I fear this could break things that rely on these > scripts output. > > https://docs.python.org/2/library/warnings.html#warnings.warn > > I'm not sure how to prevent this kind of issues though. > > About official deprecation notices, I figure the decision must be made > by maintainers and/or the technical board. > Yes. I'd suggest for 20.05 perhaps putting a deprecation notice in the docs and then later (20.08) putting warnings in the code. Perhaps full removal of support should be done for 20.11, or do we need one more LTS release with the support still present? /Bruce