ok, thanks. But now I did "make" inside the py3 virtualenv. So I have a copy of sage build using py3 (do I ? I am not sure at all. It spend a lot of time building python2.7). And still the same imports of cython modules fail. And sage runs and works, but behaves in a totally "python2" way, for instance "print 5" works.
So could please somebody give me *explicit and detailed instructions* on how I should try to build sage with python3 in a py3 virtualenv, as I asked in my first question. Frederic Le vendredi 10 juin 2016 21:30:22 UTC+2, Volker Braun a écrit : > > Afaik this is the expected result: Compiled modules (both bytecode pyc or > binary so) are versioned and will not be loaded if there is a version > mismatch. > > > > On Friday, June 10, 2016 at 3:10:56 PM UTC-4, Frédéric Chapoton wrote: >> >> ok, sorry for being so dumb and unclear. Please be patient. Let me try to >> be more clear. >> Currently I do that: >> >> * enter a python3 virtual env (using source mypy3/bin/activate) >> * cd sage/src >> * launch ipython >> * import sage >> * from sage.interfaces.all import * >> resulting in >> ImportError: No module named 'sage.misc.lazy_import' >> >> So my question is: what is the cause of this error ? The same error >> happens for several cython modules. >> >> Frederic >> >> >> Le vendredi 10 juin 2016 20:59:31 UTC+2, Volker Braun a écrit : >>> >>> Whats your question >>> >>> a) you want to build Sage in a py3 environment? Then build Sage in a py3 >>> environment. What hat do you mean by "flag to pass to make"?? >>> >>> b) you want to build Sage in a py2 environment but you want Sage to >>> build its own Python 3. Then run "SAGE_PYTHON3=yes make" >>> >>> >>> >>> >>> >>> >>> On Friday, June 10, 2016 at 2:37:43 PM UTC-4, Frédéric Chapoton wrote: >>>> >>>> Sure, but how can I try ? Is there something like a flag to pass to >>>> make ? >>>> >>>> Le vendredi 10 juin 2016 20:19:38 UTC+2, Volker Braun a écrit : >>>>> >>>>> Sage is supposedly requiring Python 2.7 or 3.3+ to build, but it isn't >>>>> tested with py3 so its unlikely to actually work. >>>>> >>>>> >>>>> >>>>> On Friday, June 10, 2016 at 2:10:38 PM UTC-4, Frédéric Chapoton wrote: >>>>>> >>>>>> Hello, >>>>>> >>>>>> What is the correct way to start trying to build sage in a python3 >>>>>> (virtual) environnement ? >>>>>> >>>>>> When I do a "make" inside a py3 virtual env, sage just setups its own >>>>>> environnement, using py2, of course. >>>>>> >>>>>> When I try to import parts of sage from an ipython3 session, I run >>>>>> into several things: >>>>>> >>>>>> * first one is #20706. >>>>>> >>>>>> * another one is the fact that cython extensions are not available, >>>>>> so that I get messages like >>>>>> >>>>>> ImportError: No module named 'sage.misc.lazy_import' >>>>>> >>>>>> Is there a way to tell sage to try to build using py3 ? >>>>>> >>>>>> Frederic >>>>>> >>>>> -- 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.
