[pypy-dev] Policy on Python 3 and Python 2 executable names

[Amaury Forgeot d'Arc]

2011/8/30 Aaron DeVore <aaron.devore at gmail.com>

> Possible solution [who uses it for CPython]:
> 1) pypy arbitrary, pypy2 for Python 2, pypy3 for Python 3 [PEP 394, Gentoo]
> 2) pypy for Python 2, pypy3 for Python 3, no pypy2 [Debian family]
> 3) pypy for Python 2, pypy2 for Python 2, pypy3 for Python 3 [Red Hat
> family]
> 4) pypy for Python 3, pypy2 for Python 2, pypy3 for Python 3 [Arch Linux]
>
> I prefer #1 because it sticks with PEP 394 and is future-proof. #2 and
> #3 take away future flexibility. #4 is a horrible, horrible idea at
> present.
>

As far as I care, #1 also looks better to me, because it follows CPython
conventions.

But the ultimate solution is certainly:
0) python for arbitrary PyPy, python2 for PyPy 2, and python3 for PyPy 3!

-- 
Amaury Forgeot d'Arc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20110831/ef317aa4/attachment.html>