From owner-freebsd-python@FreeBSD.ORG Thu Aug 1 19:14:16 2013 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2CF8C4A2; Thu, 1 Aug 2013 19:14:16 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-ee0-x22c.google.com (mail-ee0-x22c.google.com [IPv6:2a00:1450:4013:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6516C2582; Thu, 1 Aug 2013 19:14:15 +0000 (UTC) Received: by mail-ee0-f44.google.com with SMTP id b47so1210358eek.31 for ; Thu, 01 Aug 2013 12:14:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:mime-version :content-type:content-transfer-encoding; bh=utRiKs6SJV05Cij8d9jgdHK96UtsnDSfgRPPnsm3HdI=; b=FXF+JDazcjFGIzGJWTudhu07izqVqzKfBfG2GaEPIZyka1y86saJgGGypZb2NOTxvW hMq3xc9Py6963kxjJ3nvClYBRBCOj7OhGa8Tzrw33zmEgDn4Wv/CKqTEg4sFQw2RfTzj EsJLzKt+jwAddAWm5mrmBvbRPamxXxjYmo3/3WZAejBwndqExmBmbqXXEDg909TTnEYE yg2bTEikrFOyGBTPcrUvj9Ep+0K3RKWQt2dOllMfAmjXpheE1IL5AyY9fhxz0hekXI0G L2l0+LJKXVRPltHNEFqwafV2NTz8iq2CWM63jaCtxJcRNaAyvkLvdugOnhSpNNB+gC5r EnmQ== X-Received: by 10.14.48.5 with SMTP id u5mr2687005eeb.89.1375384453642; Thu, 01 Aug 2013 12:14:13 -0700 (PDT) Received: from dragon.dg ([197.87.211.201]) by mx.google.com with ESMTPSA id r54sm6422653eev.8.2013.08.01.12.14.11 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 01 Aug 2013 12:14:12 -0700 (PDT) From: David Naylor To: bdrewery@freebsd.org, eadler@freebsd.org, python@freebsd.org Subject: Naming of lang/pypy and lang/pypy3 Date: Thu, 01 Aug 2013 21:14:05 +0300 Message-ID: <1595859.oJfAmeEhYc@dragon.dg> User-Agent: KMail/4.9.5 (FreeBSD/9.1-RELEASE; KDE/4.9.5; amd64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart31260872.jEZ54PRYZj"; micalg="pgp-sha1"; protocol="application/pgp-signature" Content-Transfer-Encoding: 7Bit X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2013 19:14:16 -0000 --nextPart31260872.jEZ54PRYZj Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Hi All, The pypy team have released a version of pypy that supports python-3.2 (while the existing port supports python-2.7). I would like to quickly talk about two concepts here: * python language version (such as python-2.7, python-3.2, etc) * python implementation version (such as pypy-2.1, jython-?.?, ironpython-?.? and cpython-2.7) Currently the only supported implementation of python in bsd.python.mk is cpython and bsd.python.mk assumes the implementation and language version is the same. Of note, pypy seems to be the only implementation who's version does not match the language. I would like to eventually teach bsd.python.mk about different implementations, so with that in mind the current situation for pypy is: The pypy library directory and binary are suffixed with the implementation version (currently 2.1) however with pypy3 keeping the same version as pypy (and pypy32.1 is just confusing) how should I handle the version numbering? I could think of: a) use the language version as the suffix (i.e. pypy2.7 and pypy3.2) b) use a combination of the two (i.e. pypy2.1-2.7 and pypy2.1-2.7) c) use some other numbering scheme I currently prefer using option (a). Your thoughts? Regards --nextPart31260872.jEZ54PRYZj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAlH6s4AACgkQUaaFgP9pFrIKcgCbBCmSfFRV3o9Xnx6j1/Mo+J3s M5gAn0aeuiLbU3z0CKZUdWbXs1QKi7YM =1EQs -----END PGP SIGNATURE----- --nextPart31260872.jEZ54PRYZj--