From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 919E313888F for ; Wed, 21 Oct 2015 00:57:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C6AACE0848; Wed, 21 Oct 2015 00:57:02 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2EEB5E07A3; Wed, 14 Oct 2015 14:53:09 +0000 (UTC) Received: from pomiot (77-254-165-0.adsl.inetia.pl [77.254.165.0]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 1423E340940; Wed, 14 Oct 2015 14:53:03 +0000 (UTC) Date: Wed, 14 Oct 2015 16:52:47 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev-announce@lists.gentoo.org Cc: Mike Gilbert , Gentoo Dev , Gentoo Python Project Subject: [gentoo-dev-announce] Re: [gentoo-dev] Python 3.5 is in, Python 3.3 deprecation Message-ID: <20151014165248.6aea77a8.mgorny@gentoo.org> In-Reply-To: References: Reply-To: Gentoo Dev Organization: Gentoo X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo development announcement list X-BeenThere: gentoo-dev-announce@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/v.wH.5oBE6KQ76EhH5oCYZg"; protocol="application/pgp-signature" X-Archives-Salt: 99db39bd-d33f-4fdd-b831-43fecd501e8b X-Archives-Hash: 6818ba7d0ff829800ee4faecb60c329c --Sig_/v.wH.5oBE6KQ76EhH5oCYZg Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable (putting this on announcement board since it seems to be a major misunderstanding that causes a lot of extra work) Dnia 2015-10-04, o godz. 10:11:48 Mike Gilbert napisa=C5=82(a): > Python 3.5 has been added to ~arch this morning. Please feel free to > test and add python3_5 to PYTHON_COMPAT as appropriate. Please do not revbump packages unnecessarily, and do not drop keywords when adding python3.5 support unless it is absolutely necessary. The relevant USE flags are stable-masked, so it's completely correct to add it to PYTHON_COMPAT on stable packages. The only reason to drop stable keywords and revbump is if you have to patch the package in order to fix python3.5 support. However, this still does not require dropping of ~arch keywords, so please do not do that. If a dependency of your package has lost keywords due to a version bump, please try adding python3.5 support to the older version of the dependency rather than removing keywords from reverse dependencies. Also please note that we've just fixed keywords on a lot of Python packages. So in case you see some keyword mis-sync, please update your checkout first. > Also, to keep the number of supported implementations manageable, I > would like to deprecate Python 3.3. This means that it should not be > added to PYTHON_COMPAT in new packages. Does anyone object to this, or > have some reason we should keep it as "supported"? A minor clarification here too: please avoid adding it to new packages (unless really required -- e.g. python3.4 completely unsupported) but please *do not* remove it from existing packages yet. Implementation removal always carries huge reverse dependency problems. This is why we keep the implementation deprecated until it's ready to go, and then package.use.mask the relevant flag and afterwards remove it via eclass. This way, the removal is atomic and developers don't have to work hard on keeping dependency tree sane. > See the wiki for the current status of python implementations. >=20 > https://wiki.gentoo.org/wiki/Project:Python/Implementations --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/v.wH.5oBE6KQ76EhH5oCYZg Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJWHmxBXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOLMMQAJbW/9xuTVKfE4Nxu7RVf9D3 PojahNDD4sz4PTZuCMNyaU4BHGexe3+GSpqlqre2oBckU7UBYxffhD400I7nxDzP 76ZplERWfNs1CFjbyoTgnzJBQVdqQUXFpK1K0pD4bGuivSd+DVV0bHHSfCQqCpUq uNAcvnwEGDNSWbtVT3bBuKW0YIHYEjV57Oh1B3J9FzuBsL8un/gOPlqYRmAaiXz2 xjCiK7xHpXfD59aSxN+OPgAop+7kosaVVHUdpr3iBgG83oIbp6+TiuOpN391VMwo +6/qT6/sQz32qUDDuGS+n9GRy2DFcAd4JX4RVXhOgNQnnE5oR4VrXoNo+1PCtGeV ziAggQxbve48CrRpqwMi8r2epsDJwi/2WGiah3mknnt29tATloMGMVDlaAMRQ0WI WHrYwR/yTGneDlY29IzhevjtxBvtbxq2xI8cPm+oM5ZJkm2Q6WfeCisBFe6MPD+A WY3kZkuHzsEfYYc54sc/3oLrRtGJGp87fYUNAhVyzw5KMDy24NsgxtyHX0uoWoOs JIFGXOhHeQ157BBX57SBD9D06zwABPh7hcYkKdXEkGWaZmqOHZuD1ejCqjTUUSMB ulY3JNrBTbcP5nCQfnMp8pNtDfeNnCiN8XLwcPZlxNW7O0nx4qxydsGoPAiFGOuG KWktcqYmZn718yuaay9j =A/4L -----END PGP SIGNATURE----- --Sig_/v.wH.5oBE6KQ76EhH5oCYZg--