From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brett Gilio Subject: Re: the upcoming Great Python2 =?utf-8?Q?Purge=E2=84=A2?= Date: Thu, 27 Dec 2018 08:49:17 -0600 Message-ID: <87h8ez10uq.fsf@posteo.net> References: <20181226093812.GR2581@macbook41> <20181227043841.GA5572@jasmine.lan> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54945) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gcWyo-0001nP-BU for guix-devel@gnu.org; Thu, 27 Dec 2018 09:49:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gcWyl-0003St-43 for guix-devel@gnu.org; Thu, 27 Dec 2018 09:49:46 -0500 Received: from mout01.posteo.de ([185.67.36.65]:36250) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gcWyk-0003PJ-QA for guix-devel@gnu.org; Thu, 27 Dec 2018 09:49:43 -0500 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 67839160060 for ; Thu, 27 Dec 2018 15:49:39 +0100 (CET) In-reply-to: <20181227043841.GA5572@jasmine.lan> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Leo Famulari Cc: guix-devel@gnu.org Leo Famulari writes: > On Wed, Dec 26, 2018 at 11:38:12AM +0200, Efraim Flashner wrote: >> We're now about a year out from the official EOL for python2 (Jan 1, >> 2020). So far we've been not adding python2 variants of packages that >> are new unless they're actually needed for something. Do we want to >> start removing python2 packages when updating other packages if they are >> leaf packages? > > This was previously discussed here: > > https://lists.gnu.org/archive/html/guix-devel/2018-06/msg00237.html > > That discussion didn't go very far. As you mentioned, the consensus > seemed to be that we 1) relax the policy of always providing both Python > 2 and 3 packages and 2) we'll act when we need to. > > My opinion is that we should remove Python 2 packages after the upstream > EOL announcement if they are causing trouble somehow. > > But I don't think we need to remove them en masse. We offer many other > packages that are basically abandoned upstream, so I think it will be > okay to keep the Python 2 packages as long as there are no bugs or if > they are maintained somehow. I think we could also just move them to a different Guix channel entirely as a sort of legacy-support option. I am almost positive somebody among us would be willing to maintain them. Could be better than everybody wanting to maintain their own channel for it. Also, on a side note, how would this work for the python importers? Would we stop offering python2 substitutes on the build servers? There are some other questions here that I think aren't getting addressed. Brett Gilio