From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SemOs-0006By-Dq for garchives@archives.gentoo.org; Wed, 13 Jun 2012 12:10:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 43BB4E05E8; Wed, 13 Jun 2012 12:09:50 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 16855E05E8 for ; Wed, 13 Jun 2012 12:09:50 +0000 (UTC) Received: from pomiocik.lan (p14.ppp.polbox.pl [213.241.7.14]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 3A0741B4034; Wed, 13 Jun 2012 12:09:47 +0000 (UTC) Date: Wed, 13 Jun 2012 14:11:07 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: Dirkjan Ochtman Cc: gentoo-python@lists.gentoo.org Subject: Re: [gentoo-python] New eclass: obsoleting old python versions Message-ID: <20120613141107.1d48ecc4@pomiocik.lan> In-Reply-To: References: Organization: Gentoo X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Discussions centering around the Python ecosystem in Gentoo Linux X-BeenThere: gentoo-python@gentoo.org X-BeenThere: gentoo-python@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/q8eI.03MBvzeZpeB3jol716"; protocol="application/pgp-signature" X-Archives-Salt: c48ce697-aa18-41d7-9c39-c024046c2358 X-Archives-Hash: 435739e94155782b48f4118575b4b0e2 --Sig_/q8eI.03MBvzeZpeB3jol716 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, 13 Jun 2012 11:16:45 +0200 Dirkjan Ochtman wrote: > Additionally, the new eclass seems to think of pypy1_7, pypy1_8 as > different. We should probably have something that says, "this ebuild > supports python-2.7-equivalent pypy". Are they equivalent API-wise? In other words, is it guaranteed that if a particular Python extension (written in C) compiles with 1.8, it will compile with 1.7 and vice-versa? > Proposal: >=20 > - Add python2_7_pypy atom for PYTHON_COMPAT, expands to a list of pypy > versions which is fixed in the eclass. Maybe we could just assume pypy1_7 means 1.7+ but older than next pypy1_x defined. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/q8eI.03MBvzeZpeB3jol716 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAk/Yg2AACgkQfXuS5UK5QB3ItAQAg/fnDzVrsDDxBdbr7gk+DD5Q 5bKhhxh5cyvb8/S1CqwrMTchHHm/qSKMTie7TaiJtHGFuCtyMytwj+V15O9YpIAo Qu7oOoaHY0Z7MzhS7/Hpguqb2isBfnikoF9hokUbCXIsZLEhi6dCDiJVGOQXG4wZ 2mu6pS7C9nIka2F3kk8= =w3/3 -----END PGP SIGNATURE----- --Sig_/q8eI.03MBvzeZpeB3jol716--