From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: the upcoming Great Python2 =?utf-8?Q?P?= =?utf-8?B?dXJnZeKEog==?= Date: Wed, 26 Dec 2018 23:38:41 -0500 Message-ID: <20181227043841.GA5572@jasmine.lan> References: <20181226093812.GR2581@macbook41> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:50267) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gcNRe-0002ZI-0q for guix-devel@gnu.org; Wed, 26 Dec 2018 23:38:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gcNRZ-0001Es-9o for guix-devel@gnu.org; Wed, 26 Dec 2018 23:38:53 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:45651) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gcNRZ-0001By-1a for guix-devel@gnu.org; Wed, 26 Dec 2018 23:38:49 -0500 Content-Disposition: inline In-Reply-To: <20181226093812.GR2581@macbook41> 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: Efraim Flashner Cc: guix-devel@gnu.org --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlwkV04ACgkQJkb6MLrK fwjeig/5AWpnbfGAxeIeTNahoR16jzE3yNv/+YvEbxBe0npHPvklcpi2gzMoIL3K 3xH5I/QjemwJYRL2bT0maLrEcFuhE2UvXpfEV8nMWIqK9Fymli9fYNBarr/HaMNZ 0vXLF4I+DQ3RVA8/GbFiIbv+DrcUL2hhQrto5fZewiyeGOr5fG34yZQ13xuUjUXt uoGwYux9HHxEu0kPjPVLiTBQS9FUWVplievTtnP2t8Qf758S2Vr+mAXa5FMxImDc 7417mva8991htYBJbAl8dZmSDLQI3VjmRmYp9tLeLIKUh5Ot/aXo2KxTHVfDe3N/ Edknu0SX+00Lf7U+Dw7isNya380zAh4TbC7NPJGcPEw9I1+QfJnCpA7YuM+++YdU DoHZJRrd8sntQuHnI8FygbHE8yFOpdUPHVP1pljgpLizqLasPGDG4F1bY0SJ3k0U agmISBj8jqRNudv51try3AHitJCwgYXivzTnfJvIL+XcKAi8VR1zSXZEI2GY0D8w 1ndphOjQZCcyvK+oj6szmXbFbcv1SQuLNnClI0hihAhbUjcoE4RsqAT4a7bqX4yU r87Pptd9f+Ht+JfRiE6vilVpTAAhXrrG/htFxKubxalZnWnB/JhSDt1GOxbbhBr8 X6S3npRazYzjSWY4Id4IoWXL7icuYI64UjVANYGvkeSoLOLB7YM= =bSNJ -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e--