Tue 2018-05-29 15:59:27 UTC, Frédéric Chapoton:
>
> here is a small report on the slow progress towards Python3-compatibility
> for Sage.
>
> Sage is already building and starting with python3 since some time 
already.
> It is explained in https://trac.sagemath.org/ticket/15530 how to get
> a python3-sage. One can note an even longer startup time (sigh).
>
> There has been recent progress on the pexpect interfaces and lib 
interfaces,
> so this sage3 is now somewhat usable. Try it !

Hi Frédéric, thanks for the hard work on making Sage Python3-compatible!
I succeeded in building Sage 8.3.beta1 both for Python2 and for Python3.
I started using "SagePy3" for regular work, switching to "SagePy2" only
when "SagePy3" won't do the work. I thus noted there's a fair amount one
can already do with "SagePy3".

> Our next goal is to get the documentation build. After that, one will have
> to make all doctest pass, but we are still a long way from that.
> Another interesting step would be to be able to launch the jupyter 
notebook
> with sage3. Currently, it looks for the sage kernel in the python2 library
> (no ticket yet).
>
> The current result of trying to build the doc can be seen here: 
>
> 
https://patchbot.sagemath.org/log/0/Ubuntu/18.04/x86_64/4.15.0-20-generic/petitbonum/2018-05-27%2021:55:21?plugin=docbuild
>
> Apparently, we are not so far to manage building the documentation. Two
> important issues, responsible for many errors in docbuilding:
>
> (A) fix some heavy problem of hash in the manifolds code, see
> https://trac.sagemath.org/ticket/25393
>
> (B) need to reactivate the build of sagenb in python3, see
> https://trac.sagemath.org/ticket/22431
>
> Ticket 22431 above need people to check (1) that the upgraded sagenb
> works smoothly on python2 and (2) that sage3 still builds and starts
> after building sagenb.
>
> (note that even after 22341, sagenb will not work in sage3, due to some
> missing parts of twisted, that require upgrading twisted.)
>
> Does somebody care ?

I care a lot! But all I can do so far (not that it helps a lot) is build
each new beta both for Py3 and Py2 and work primarily with the Py3 one,
switching to the Py2 one only as needed.

By the way, did "SagePy3" 8.3.beta2 build for anyone? I had no luck getting
it to build under (now unsupported) macOS 10.10.5. I have to try 8.3.beta3
now that it is out.

Do we ensure each new beta builds for Py3 on supported platforms?

Maybe the announcement for each new beta on sage-release could remind
readers that https://trac.sagemath.org/ticket/15530 has the instructions
for building a Python3-based Sage?

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