Thanks for the quick response. This was going to be my next approach. I will give it a go and report back my status.
Python 3.4 works on the Edison when building from sources. Steps:
wget --no-check-certificate https://www.python.org/ftp/python/3.4.2/Python-3.4.2.tgz
tar -xvf Python-3.4.2.tgz
make -s -j2
The make process takes something like 10-15 minutes. There is no terminal output, just wait. Then, python binary will appear in the directory.
After that you could remove the link for Python 2.7
And create a new link to Python 3.4
ln -s /home/root/Python-3.4.2/python /usr/bin/python
I tried copying the mraa files in Python 3.4 library with no success, as Peter mentioned in the previous post
Python 3.4 seems to complain about the _mraa.so dynamic library created with SWIG
It sounds like my best bet is to convert to 2.7 for the time being. Thank you for your input.
I will give this a try and report back any issues. Thank you for the advice.
your suggestion did work. I was able to get 3.4 up and running, however, as you mentioned mraa does not play with 3.4. Thanks for the help, but it looks like 2.7 is what I will move forward with.
Not sure if it would help or not, but have you tried downloading mraa sources to your Edison after intalling 3.4, and do a cmake followed by a make (see MRAA instructions up on github). I know on my machine the cmake finds my 2.7.3... Not sure what it would do if it found a 3.4 instead...