mx dependency on Python 2.7

Gilles Duboscq gilles.m.duboscq at
Sun Mar 20 18:48:02 UTC 2016

Hi Raffaello,

Python 2.x and 3.x can co-exist without any problem, there shouldn't be anything special to do besides making sure python 2.7 is installed.
No environment variables should be necessary. We use `python2.7` as mx's python interpreter and fallback to `python2` if that doesn't exist. If `python2` also doesn't exist only then do we use the ambiguous `python`.

When a distribution "transitions" to python 3.x, it just means that the `python` symlink goes to Python 3.x instead of 2.x.

We have already used mx in distributions where Python 3 is the default without any problem.

I don't know of any plan to port mx to Python 3.


On 20/03/16 15:51, Raffaello Giulietti wrote:
> Hello,
> I've a rather superficial understanding of both mx and Python. What I've
> got, however, is that mx depends on Python 2.7 and might not work on
> Python 3.x.
> The upcoming 16.04 LTS release of Ubuntu, planned for 2016-04-21, will
> transition to Python 3.
> I'm not sure if Python 2.7 can then co-exist transparently with Python
> 3. Stated otherwise, is it simply a matter of configuring the
> environment vars to keep mx running correctly on a system with both
> Python 2 and Python 3 installed?
> More forwardly thinking, are there plans to move mx to Python 3?
> Greetings
> Raffaello

More information about the graal-dev mailing list