On Thursday, May 25, 2017 at 10:08:21 AM UTC-7, Kwankyu Lee wrote: > > The successful launch with my built of sage with python3 seems well > explained by John. > > On Thursday, May 25, 2017 at 5:37:10 PM UTC+2, Frédéric Chapoton wrote >> >> 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. >> > > This is painful. > > A novice question about design: do we aim to make sage (1) "buildable > either with python2 or with python3" or (2) "runnable either with python2 > or with python3". Am I clear enough? If (2), then you build once and then > sage can be run with either python2 or with python3. I prefer (2), but I > don't know which is easier to achieve. >
The current approach has been (1). With (2), if we don't mind using more disk space and having a longer build time, I think the Python libraries can be dealt with: just build each twice, for local/lib/pythonX.X/site-libraries with X.X=2.7, 3.6. We do this for setuptools and pip already. Are there other components of Sage that end up in local/lib (not tagged by the Python version) that depend on the version of Python? John -- 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.
