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
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 m
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
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
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, 201
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) environn
