From owner-freebsd-python@FreeBSD.ORG Sat Aug 3 14:00:38 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 0DBCF503; Sat, 3 Aug 2013 14:00:38 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-ee0-x229.google.com (mail-ee0-x229.google.com [IPv6:2a00:1450:4013:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6AE392397; Sat, 3 Aug 2013 14:00:37 +0000 (UTC) Received: by mail-ee0-f41.google.com with SMTP id d17so795920eek.14 for ; Sat, 03 Aug 2013 07:00:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=OWps3r2KoBxzf7vMUWPfva0lF43PMhlFTz9tqto4tdU=; b=z/BAYPsgXrzYqiAfBpi0f4GZui/eI246HCfEOOu5MU2iPfb3lnFOEJsqzIgbM6T/9b Ee01hS2ilF0/MNmJSY+zoh7UNHs4T5dXe7XQYKFNkHi/FyrlKaq7ePDezQqN6GEveJVG TnnzoA/u+JhXSM6bH+eAWbv+upF+Waw5M6VzhgY35EaW0BYhYKSd/2c39ou9UzpzPrP5 0CM4pGqvmYeaTZqI1ix9XqV8Xa4wzcc+D9veHBg8ReBGG57vEITe+9ZC/bDRGtXOslPG dylSY2VKcwlFJLQxhmRuelcLDmy2Gc2H6C6pBUaFjUXbPyObnY8VVmiXP0ELXDGjF2/7 Ai4Q== X-Received: by 10.14.204.194 with SMTP id h42mr9709068eeo.47.1375538435550; Sat, 03 Aug 2013 07:00:35 -0700 (PDT) Received: from dragon.dg ([197.87.211.201]) by mx.google.com with ESMTPSA id e1sm7796807eev.8.2013.08.03.07.00.33 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 03 Aug 2013 07:00:34 -0700 (PDT) From: David Naylor To: Marcus von Appen Subject: Re: Enabling ports to be installed for different python versions Date: Sat, 03 Aug 2013 16:00:27 +0300 Message-ID: <4794970.92XoZoQXFi@dragon.dg> User-Agent: KMail/4.9.5 (FreeBSD/9.1-RELEASE; KDE/4.9.5; amd64; ; ) In-Reply-To: <20130803125804.GC1280@medusa.sysfault.org> References: <20130803103245.GA62768@medusa.sysfault.org> <3135486.lOCflO8WFc@dragon.dg> <20130803125804.GC1280@medusa.sysfault.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2131470.HuaFo0ZK1R"; micalg="pgp-sha1"; protocol="application/pgp-signature" Content-Transfer-Encoding: 7Bit Cc: freebsd-python@freebsd.org 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 14:00:38 -0000 --nextPart2131470.HuaFo0ZK1R Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="ISO-8859-1" On Saturday, 3 August 2013 14:58:04 Marcus von Appen wrote: > On, Sat Aug 03, 2013, David Naylor wrote: > > On Saturday, 3 August 2013 12:32:45 Marcus von Appen wrote: > > > Support for non-CPython implementations: > > > > > > - A mid-term goal should be to offer support PyPy in USE_PYTHON, etc. > > > > > > This can introduce a new PYTHON_PKGNAMEPREFIX and SUFFIX and should > > > have only a minimal impact on implementing the change, once everything > > > else has been done. > > > > I don't think we need to limit the scope to only PyPy, there is also > > IronPython and Jython (perhaps longer term goals). I have the following > > > > suggestions for PYTHON_PKGNAMEPREFIX: > > - ppyXY for PyPy > > - p3pyXY for PyPy3 > > - ipyXY for IronPython > > - jpyXY for Jython > > > > where XY is the implementation version. > > I left out IronPython and Jython intentionally, since they are barely > usable from a module compatibility point of view (especially for Python > 2.7+). Thus my current focus is on getting CPython and PyPy (or PyPy3) > up and running as default python interpreters for FreeBSD. Once I have "finished" my remaining big ports I would like to move on to getting IronPython and Jython working nicely with Ports. But that is at least months away... > > I'll happily act as liaison between the Python/FreeBSD PyPy teams if > > needed. > I was unaware that there are seperate teams for that ;-). I would > consider PyPy to belong to the FreeBSD Python team as well as Jython, > IronPython, Cython, PyRex... By "PyPy team" I meant upstream PyPy team. I do agree with your expectation: as the sole PyPy maintainer I do consider myself part of the PyPy team. --nextPart2131470.HuaFo0ZK1R 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) iEYEABECAAYFAlH9DP4ACgkQUaaFgP9pFrLp8gCfWIue+RgV5rfrmbTnhxy+Jqyu Z2sAn34UVDDNBC88F0+3GhVg0bpevDf+ =4Hlz -----END PGP SIGNATURE----- --nextPart2131470.HuaFo0ZK1R--