> > > > *STATEMENT *: I would to advocate that **every developer switch to > python3 > > NOW**. > > How? > > To make my question more precise: For production I would like to > keep a python 2 installation of Sage.
I am pretty sure you would be rather happy working only with python3. > So, given my existing Sage > installation, what would be the easiest way to create a second > installation with python 3 that is automatically configured to work > well with "git trac"? I guess it is some kind of git clone. Also I > don't know what make target is needed. > > How to build sage with python3: first "git clone" into another dir, say "sage3" then inside this dir: make configure ./configure --with-python=3 make build The first two lines need only be used once and for all. concerning the tests, there is currently a partial test target that ensure that thing know to pass still pass if you want to run all tests, then all course, you will meet failures in some parts of 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.
