From: "Michał Górny" <mgorny@gentoo.org>
To: Marien Zwart <marienz@gentoo.org>
Cc: gentoo-python@lists.gentoo.org, python@gentoo.org
Subject: Re: [gentoo-python] Re: Naming of PyPy and PyPy3 executables
Date: Mon, 19 Aug 2013 13:07:07 +0200 [thread overview]
Message-ID: <20130819130707.33f23608@gentoo.org> (raw)
In-Reply-To: <CAEWfL_RyVd+E3wbdY_EyJ9WeQVq-nRyqTeHJy4vAjm_Zn6yfBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]
Dnia 2013-08-19, o godz. 20:43:05
Marien Zwart <marienz@gentoo.org> napisał(a):
> On Mon, Aug 19, 2013 at 8:29 AM, Michał Górny <mgorny@gentoo.org> wrote:
> > This raises the question: how should we name our PyPy executables?
> > While I really like the 'pypyX.Y' idea, I don't really want to see
> > 'pypy32.1' :). We could go for 'pypy-X.Y' and 'pypy3-X.Y' but that would
> > be inconsistent with CPython (pythonX.Y) and Jython (jythonX.Y0).
> > A somehow ugly alternative would be to use 'pypy-cX.Y' and 'pypy3-cX.Y'
> > but that is quite a custom invention.
>
> I believe Jython follows CPython's versioning. If PyPy supports python
> 2 and 3 using differently-named binaries from the same PyPy version
> (which doesn't follow any particular CPython version) we'll either
> have to deviate from PyPy's version number in how we name our
> binaries, or be inconsistent with CPython/Jython in how we name them.
>
> I think your pypy-x.y / pypy3-x.y suggestion could work.
>
> An alternative would be to include the version of the bundled CPython
> stdlib into the name. Unfortunately (for the naming scheme) I think
> we'd still want to support simultaneous installation of different PyPy
> versions with the same bundled stdlib version, so we'd then have to
> stick both into the installed binary's version number (pypy2.7-2.1,
> pypy3.2-2.1). We could then add some symlinks, so we'd have pypy3.2
> and pypy3 counterparts to python3.2 and python3. Having those would
> appeal to me, but (if we want to support multiple PyPy versions per
> CPython stdlib version) that's a lot of extra wrappers floating
> around.
That sounds like a lot of effort with no real gain.
> So I think your simpler approach (pypy-2.1, pypy3-2.1) would be best
> for now. We'll have to keep an eye out for what other distros and
> upstream do.
Other distros didn't support having multiple PyPy versions before.
I mean, we can expect them to have just one PyPy + PyPy 3.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-08-19 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 22:29 [gentoo-python] Naming of PyPy and PyPy3 executables Michał Górny
2013-08-18 22:34 ` [gentoo-python] " Mike Gilbert
2013-08-19 10:43 ` Marien Zwart
2013-08-19 11:07 ` Michał Górny [this message]
2013-08-19 13:04 ` Dirkjan Ochtman
2013-08-20 14:20 ` [gentoo-python] " Arfrever Frehtes Taifersar Arahesis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130819130707.33f23608@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=marienz@gentoo.org \
--cc=python@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox