From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: the upcoming Great Python2 =?utf-8?Q?Purge=E2=84=A2?= Date: Mon, 18 Feb 2019 12:07:08 +0100 Message-ID: <87h8d1we1v.fsf@elephly.net> References: <20181226093812.GR2581@macbook41> <20190218095619.GC7206@macbook41> <87o979wftc.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:51483) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gvglp-0006By-19 for guix-devel@gnu.org; Mon, 18 Feb 2019 06:07:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gvgll-0003mR-N0 for guix-devel@gnu.org; Mon, 18 Feb 2019 06:07:31 -0500 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21084) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gvgli-0003jA-22 for guix-devel@gnu.org; Mon, 18 Feb 2019 06:07:27 -0500 In-reply-to: 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: Konrad Hinsen Cc: guix-devel@gnu.org Hi Konrad, >> Konrad, going forward it might be reasonable to keep copies of required >> Python 2 packages in your channel. We aren=E2=80=99t going to remove Py= thon 2 >> packages now, but in the future we may not be able to fix unmaintained >> packages and may have to remove them. > > "My channel" doesn't exist (because I haven't yet found the time to > figure out how to set up and manage a channel, although it's been on my > to-do list for a while). I=E2=80=99d be happy to assist. > But... how about splitting off *all* of Python 2 and everything that > depends on it into a separate channel, which would then be maintained > by a separate team? Currently this is not feasible, in my opinion, as a lot of packages in Guix still depend on Python 2 for some reason or the other. When Python 2 reaches EOL, however, I think this would be a reasonable thing to do. -- Ricardo