I have made a git branch (public/ugly_python3) with the ad-hoc changes..With this, one meets as wanted (this is my aim) a first real problem in sage-code (namely unicode in sageinspect for the moment).
Frederic Le jeudi 25 mai 2017 17:37:10 UTC+2, Frédéric Chapoton a écrit : > > Hello, > > I would like the design discussion to take place now, for sure. I would > like that we have a clean way to build and run sage with python3, so that > we can concentrate on fixing the many remaining issues inside sage code > itself, with a python3 build correctly in place. The road towards a full > python3 sage is still quite long, and my motivation gets weaker, as it > seems that not so many people care about that. > > The temporary fix you suggest does not solve the issue, maybe because I > did not comment the "remove_stale_file" line before compiliing. My problem > is not to find ad-hoc fixes, but to fix the build in a proper way. I do not > have the technical ability to do that myself. To those who know, please > open trac tickets and propose branches. > > Frederic > > Le jeudi 25 mai 2017 17:06:00 UTC+2, John H Palmieri a écrit : >> >> >> >> On Thursday, May 25, 2017 at 1:49:34 AM UTC-7, Frédéric Chapoton wrote: >>> >>> ok, now with 8.0.b8, you can just do >>> >>> "export SAGE_PYTHON3=yes" >>> >>> and then "make build". This should succeed, with no error message. >>> >>> Then try "./sage" >>> >>> This fails with some traceback about not finding sage.repl.interpreter. >>> >>> Once again, can *please* someone help to fix that ? >>> >> >> I suggested a problem before: the script sage-ipython, which is used to >> start Sage, has as its first line #!/usr/bin/env python, and therefore runs >> Python 2, not Python 3. The next interesting line in that script is >> >> from sage.repl.interpreter import SageTerminalApp >> >> Since you have built Sage with Python 3, then the Sage library is >> installed in local/lib/python3.6/site-libraries/sage, so Python 2 doesn't >> find it. Is that not the problem? >> >> A temporary fix: change to #!/usr/bin/env sage-python23. A longer term >> fix: we have to decide how to run Sage with Python 3. Maybe create a script >> sage-ipython3 which uses #!/usr/bin/env python3 and a command-line option >> for sage which tells it to use Python 3? We need a design discussion about >> this. >> >> -- >> John >> >> >> >>> >>> Frederic >>> >>> Le vendredi 19 mai 2017 18:51:46 UTC+2, Frédéric Chapoton a écrit : >>>> >>>> Dear all, >>>> >>>> We have almost reached the state of vanilla sage building with >>>> SAGE_PYTHON3=yes (this does not mean working !). But something seems to go >>>> wrong, and I would like help to find and fix the current problem. >>>> >>>> So, for people that want to do something else than answering polls, you >>>> can try the following: >>>> >>>> In a separate install of sage, on top of 8.0.beta7, apply >>>> >>>> https://trac.sagemath.org/ticket/23030 (git pull trac u/chapoton/23030) >>>> >>>> and >>>> >>>> https://trac.sagemath.org/ticket/22305 (git pull trac public/22305) >>>> >>>> then export SAGE_PYTHON3=yes >>>> >>>> and make build. >>>> >>>> This should finish succesfully, with the usual message. Then try ./sage >>>> >>>> For me, this fails with some traceback about not finding >>>> sage.repl.interpreter. Can someone help to fix that please ? >>>> >>>> Frédéric >>>> >>>> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
