PPS: if you intend to have a py2 and py3 installation it is a good
idea to have a shared $SAGE_ROOT/upstream/ repository (where
package tarballs are downloaded). This can be done via a simple
simlink in the py3 installation.
Maybe we could create a configure option --with-upstream=PATH for
this?
Vincent
Le 27/01/2019 à 14:56, Frédéric Chapoton a écrit :
git clone git://github.com/sagemath/sage.git sage3
Le dimanche 27 janvier 2019 14:50:22 UTC+1, Simon King a écrit :
Hi Vincent,
On 2019-01-27, Vincent Delecroix <20100.d...@gmail.com <javascript:>>
wrote:
You need a different clone of your git repo, let say sage-py3.
How to do so most easily, so that "git pull" etc. still referes to trac?
That was part of my question. Doing "git pull
/path/to/my/old/installation" would mean that I need to go to my old
installation, "git pull" (pulls develop from trac), go to the new
installation, and to "git pull" again (pulling develop from my old
installation, but NOT directly from trac).
That's awkward and could certainly be done better.
In that
clone, do
$ make configure
$ ./configure --with-python=3
Thank you!
Best regards,
Simon
--
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.
