Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 03 Aug 2013 16:00:27 +0300
From:      David Naylor <naylor.b.david@gmail.com>
To:        Marcus von Appen <mva@freebsd.org>
Cc:        freebsd-python@freebsd.org
Subject:   Re: Enabling ports to be installed for different python versions
Message-ID:  <4794970.92XoZoQXFi@dragon.dg>
In-Reply-To: <20130803125804.GC1280@medusa.sysfault.org>
References:  <20130803103245.GA62768@medusa.sysfault.org> <3135486.lOCflO8WFc@dragon.dg> <20130803125804.GC1280@medusa.sysfault.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--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--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4794970.92XoZoQXFi>