There are a number of ways in which sage assumes you only have a single version of python installed. The main reason for introducing the python3 package was so developers interested in porting sage to python 3 could easily try building sage with python 3 instead of python 2.
I just encountered this problem.... sage -i py3 ( to install python3)... broke my whole system... Is there a single "undo" operation so that I can return to my working copy?
On Wednesday, August 10, 2016 at 9:13:14 AM UTC+1, The Geeko wrote:I just encountered this problem.... sage -i py3 ( to install python3)... broke my whole system... Is there a single "undo" operation so that I can return to my working copy?do you meansage -i python3
Dima Pasechnik wrote:
> this is now https://trac.sagemath.org/ticket/21199
Is it at all supposed to be used that way? (I don't think so. IMHO
it's an optional package to use *instead* just like GMP vs. MPIR at Sage
*configure* time, not to be installed afterwards.)
On Wednesday, August 10, 2016 at 9:22:46 AM UTC+1, Dima Pasechnik wrote:
On Wednesday, August 10, 2016 at 9:13:14 AM UTC+1, The Geeko wrote:I just encountered this problem.... sage -i py3 ( to install python3)... broke my whole system... Is there a single "undo" operation so that I can return to my working copy?do you meansage -i python3this breaks sage, as it makes the symbolic link 'python' to point to 'python3' in SAGE_LOCAL/bin.To fix, it suffices to make it point to python2 instead:cd SAGE_ROOT # where your Sage is installedcd local/binln -sf python2 pythonThen everything works as before(and you may also use python3 script from 'sage -sh')