Very surprising that sage starts.. Did you really launch the sage that you 
just compiled ?

I am using Linux, and do not know anything about macs, sorry. Did you check 
that "echo $SAGE_PYTHON3" answered yes ?

Yes, another aspect of the same problem is this complete recompilation 
every time. It seems that all compiled files are just washed out for 
"cleanup" of sage.

I think we need some input from people that understand the build process. 
John already helped, but others are very welcome to give a hand. I will not 
be able to solve that, and this is the next step towards python3.

Frederic



Le jeudi 25 mai 2017 16:22:47 UTC+2, Kwankyu Lee a écrit :
>
>
>
> On Thursday, May 25, 2017 at 10:49:34 AM UTC+2, 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"
>>
>
> Following your instructions, I built sage on mac. Then sage starts with no 
> problem, strangely. So I checked the version of running python. It is 
> 2.7.13. What should I do to run sage with python3?
>
> Being unsure if sage was built to run with python3, I followed the 
> instructions once more to build again. Then sage is now compiling 457 files 
> all over again. This is not normal.
>
> Anyway, I could not reach to the point where "./sage" crashes... Any idea 
> what I missed?
>

-- 
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.

Reply via email to