From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 302BA1382C5 for ; Mon, 1 Jun 2020 21:07:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E9FEEE088D; Mon, 1 Jun 2020 21:07:44 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id ADDF4E086B for ; Mon, 1 Jun 2020 21:07:44 +0000 (UTC) Message-ID: <511f1dc86dc64a95e3d748ae48a0baa5a1f21eec.camel@gentoo.org> Subject: Re: [gentoo-dev] [RFC] Deadlines for next Python implementations From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Date: Mon, 01 Jun 2020 23:07:39 +0200 In-Reply-To: <878sh6tsto.fsf@gentoo.org> References: <406eb21bfa9f868539688a6233c364b8343f75ee.camel@gentoo.org> <878sh6tsto.fsf@gentoo.org> Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-KuUbeBNEYfBU0qCMiH6m" User-Agent: Evolution 3.36.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: 344b4eea-92c0-430a-aaed-4f523f26577c X-Archives-Hash: 19bea24b5736c4089f7659aa76a87890 --=-KuUbeBNEYfBU0qCMiH6m Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 2020-06-01 at 15:49 -0500, Matthias Maier wrote: > On Mon, Jun 1, 2020, at 15:27 CDT, Micha=C5=82 G=C3=B3rny wrote: >=20 > > 2020-08-01 Python 3.7 migration deadline > >=20 > > After this date, we lastrite all remaining packages that haven't bee= n > > ported. This gives people roughly two months, with a ping one month > > from now. > > [...] > > 2020-12-01 Python 3.8 migration deadline > >=20 > > We lastrite all the unmigrated packages. >=20 > Most of the time (guess >99%) this "porting" simply consists of > "keywording" with the new python target, i.e., a one-line change in the > ebuild. >=20 > What about we "auto keyword" all remaining packages that have a > python3_6 target but lack the python3_7 target instead? Meaning, just > add the python3_7 value to the corresponding PYTHON_*TARGET. >=20 > Given the fact how little difference there is between python3_6 and > python3_7 this seems to be the appropriate, gentler approach here. >=20 Most of these packages are unmaintained, seriously outdated and they may actually be broken with py3.7 (because they're so seriously outdated).=20 I don't see that as solving a problem, it merely shoves it under the carpet and leaves us with the same shove-under-the-carpet attitude for the next few years. I like to think of these migrations as opportunity to fix some broken ebuilds, update some packages and last rite all the things that aren't maintained. --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-KuUbeBNEYfBU0qCMiH6m Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQGTBAABCgB9FiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAl7VbhtfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM3 NkE4NDUwOTQwOThEMjhDQzhCMjZDNTYzOUFEQUUyMzI5RTI0MEUACgkQY5ra4jKe JA5gtggAid9nfSnTQHX8N+W6R2A84nikcGQU4I0iSwuXJE4CGu4OwCme2yAlXvQh fgH9QJ1AlzfFbMGxUUfDyOKztTfygRIKAoj6ktIRKFi2QgaUuD/h6Go/Bp3yybkk Sv1tCj90CqQnfIDcsQvtseKC4zbCJx9XaH/mHybUPot8mEnbEskgLc3N+ITZAni7 2IgU2fysPSMU+6QQ986afCR8xz3vtj5Tc5QuOSl6CduwCHHrgY/zrfSsDCSk1WW8 HvhieFsV4oUxwlSe4AZGPBx2JhEujUpw7iJYvgDbvURFxeWEjJdNVYU1tjHV0FiG zpDBMRqTaK+PXlkIkmSHew5g9GxMhg== =O9FQ -----END PGP SIGNATURE----- --=-KuUbeBNEYfBU0qCMiH6m--