From owner-freebsd-python@FreeBSD.ORG Sat Aug 3 16:25:14 2013 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 544D97AF; Sat, 3 Aug 2013 16:25:14 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B136526F2; Sat, 3 Aug 2013 16:25:13 +0000 (UTC) Received: by mail-ea0-f177.google.com with SMTP id f15so832745eak.36 for ; Sat, 03 Aug 2013 09:25:12 -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:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=zAwIstkYQR+jRoKYGMdFllqWUiVoMmPcooxTirRJIGU=; b=m+bMqnknxq/nh//atW1hkN7Toc4PmTB0WAwFpMqZ6p22HbYg4O+Eeqy3aTMyz1JRjk hW2/SV3lfMOWVyDz2hhoyr2fmbE0XEMnN37OWatVH/eIxD3KaSJbJKPzAUGfhfQDdpbR ffriqv1a/qyHmMlnG3xeglSb07/K9x5quVsX7yQrYi/cDgfftgEVircb7OAqG8L5c8vB 2aw+FrZ+1qjespeiiU3Ddv5Ovosirwuh4a+fuGKupwC38Cs9KoEZpfFpDSVkbqM+94rY vviGwCvNGtfKYtMqtkPAY/yFjkw5XD7utOxTDcvAemoNzOnccp8ho7SIaLbp61WR5sAD VqCg== X-Received: by 10.14.176.199 with SMTP id b47mr10043291eem.117.1375547112022; Sat, 03 Aug 2013 09:25:12 -0700 (PDT) Received: from dragon.dg ([197.87.211.201]) by mx.google.com with ESMTPSA id x3sm19780297eeu.1.2013.08.03.09.25.09 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 03 Aug 2013 09:25:11 -0700 (PDT) From: David Naylor To: freebsd-python@freebsd.org, Marcus von Appen Subject: Re: Naming of lang/pypy and lang/pypy3 Date: Sat, 03 Aug 2013 18:25:01 +0300 Message-ID: <6283190.FdUAYIpsqz@dragon.dg> User-Agent: KMail/4.9.5 (FreeBSD/9.1-RELEASE; KDE/4.9.5; amd64; ; ) In-Reply-To: <20130801195023.GA1345@medusa.sysfault.org> References: <1595859.oJfAmeEhYc@dragon.dg> <20130801195023.GA1345@medusa.sysfault.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2168369.BUPnfW8zrx"; 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: Sat, 03 Aug 2013 16:25:14 -0000 --nextPart2168369.BUPnfW8zrx Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="ISO-8859-1" On Thursday, 1 August 2013 21:50:23 Marcus von Appen wrote: > On, Thu Aug 01, 2013, David Naylor wrote: > > 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? > > a) would cause a big mismatch when users report errors to the pypy > upstream. Do not do it. > b) just looks overly complicated to me > c) naaaaaaah > > How about something like: > > pypy-2.1 (or pypy2-2.1) > pypy3-2.1 > > This would match the pypy versions perfectly in my opinion. > > (On a side note: do you mind to move pypy betas into a pypy-devel port > or such alike? The beta versions currently prevent using pypy as > more or less stable replacement for CPython). Thanks for your input. I've opted for pypy-2.1 and pypy3-2.1. I'll gladly make a -devel port for pypy (starting with pypy3-devel :-D). Could you please elaborate how the beta's are preventing pypy from being used as a replacement for CPython? Regards --nextPart2168369.BUPnfW8zrx 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) iEYEABECAAYFAlH9LuIACgkQUaaFgP9pFrI5pQCfWuxoggdapaSYdvPFTkXvgIL7 7J0AoIc4G0L02Vbh5nZDtlfdsHxeQlp5 =FXey -----END PGP SIGNATURE----- --nextPart2168369.BUPnfW8zrx--