[sage-devel] Re: Getting started with my own branch
On Aug 7, 1:06 am, Simon King wrote: > Hi Victor, > > On 6 Aug., 14:17, VictorMiller wrote: > > > Georg, Thanks. My situation is a bit unique (as William fully > > understands). Copying the sage source from sagemath.org is not an > > option that I have. Our sysadmins get the source and then build it > > and make a built directory available to us on the system. I have to > > proceed from there. > > I don't know *how* special your situation is. But certainly you do not > need to be "root" in order to build and execute Sage. > Just download the tarball in your favourite directoory in your home > tree (where you have write permissions), say, ~/foo/bar/, and build > sage there, hence: > - go to ~/foo/bar/sage-4... (whatever version it is), > - type "make" > - go for lunch Right. > - after lunch, provided sage is built, edit the file "sage" in this > folder. What you need to do is to provide an appropriate value for > SAGE_ROOT, which here is ~/foo/bar/sage-4... I'm not sure you need to do this. At least, I never have. > - Then, still being in this directory, you can start sage by ./sage Another option: I have a fixed nonexistent directory (say, ~/foo/bar/ sage/) in my $PATH, and after building sage in ~/foo/bar/ sage-4.1.1.rc1-alpha35/ or whatever, I create a symlink from there to ~/foo/bar/sage/. Then when I type "sage" from any directory, it runs this one. I keep a few others in ~/foo/bar/sage-3.4.1/, etc., in case I want to run an older version for some reason, and in this case, I just specify the full path. John --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
Hi Victor, On 6 Aug., 14:17, VictorMiller wrote: > Georg, Thanks. My situation is a bit unique (as William fully > understands). Copying the sage source from sagemath.org is not an > option that I have. Our sysadmins get the source and then build it > and make a built directory available to us on the system. I have to > proceed from there. I don't know *how* special your situation is. But certainly you do not need to be "root" in order to build and execute Sage. Just download the tarball in your favourite directoory in your home tree (where you have write permissions), say, ~/foo/bar/, and build sage there, hence: - go to ~/foo/bar/sage-4... (whatever version it is), - type "make" - go for lunch - after lunch, provided sage is built, edit the file "sage" in this folder. What you need to do is to provide an appropriate value for SAGE_ROOT, which here is ~/foo/bar/sage-4... - Then, still being in this directory, you can start sage by ./sage In that way, you can easily have various copies or different versions of sage in parallel, and they do not interfere with the Sage installation of your sysadmin. Of course, if you just do "sage", you would still get the sysadmin- version of Sage, since this is in your path. But in any directory you would be able to start your private copy of Sage by "~/foo/bar/sage-4/sage" I think this is quite common for sage-devels. Cheers, Simon --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
Can you sage -bdist a copy of sage that you don't have write permissions to? If you can, this would give you a tarball that you could then unpack in your home directory that shouldn't have any references to the original. - Robert On Aug 6, 2009, at 5:17 AM, VictorMiller wrote: > > Georg, Thanks. My situation is a bit unique (as William fully > understands). Copying the sage source from sagemath.org is not an > option that I have. Our sysadmins get the source and then build it > and make a built directory available to us on the system. I have to > proceed from there. > > Victor > > On Aug 6, 7:02 am, gsw wrote: >> On 5 Aug., 19:15, VictorMiller wrote: >> >> >> >> >> >>> Ok, I think I've found the problem. Perhaps this should point to >>> the >>> need for making clear and complete instructions about creating your >>> own copy. >> >>> I found that in my local copy there was a sage script that >>> pointed to >>> the systemwide sage. When I changed that I now get my local >>> copy. So >>> perhaps the instructions should say: >> >>> Copy the whole directory tree. Inside the top level directory there >>> is a script called sage. Edit that so that SAGE_ROOT points to your >>> local copy, and use that version of sage to run sage (e.g. by >>> making a >>> symbolic link to it in one of your local directories in search order >>> ahead of the system wide copy). >> >>> So, another question -- it seems that sage -ba didn't regerenate the >>> individual doc files, since if I do something like >> >>> EllipticCurve?? >> >>> the path that it displays is in the systemwide directories. Should >>> sage -ba do that? How do I regenerate these files? >> >>> Victor >> >> Hi Victor, >> >> a) >> Just to be sure --- this sounds like the "Guess 1" from William >> (second message in this thread) turned out to be 100% correct, or >> am I >> missing something? >> And if "Guess 1" was correct, how could we have phrased it better / >> more understandable? >> >> b) >> Regarding the EllipticCurve?? issue. Sorry for asking --- but did you >> do "sage -ba" again, after having adressed the $SAGE_ROOT problem? >> >> c) >> Generally speaking, the way of "copying" an existing Sage tree, and >> then starting to develop, is a way rarely used. So there might be >> lurking even more pitfalls yet to be discovered. >> On the other hand, building Sage from source is spectacularly easy: >> >> - download the single tar file with all sources for the current Sage >> release from sagemath.org >> - unpack the tar file in the directory of your choice >> - cd into the newly created "Sage root" directory (after possibly >> moving and/or renaming it, if you wish so) >> - type "make" (and wait a few hours) >> >> You then have the setup / the environment Sage is developed in, and >> where certainly fewer such issues as you report are to be expected. >> And *if* any problems should occur during the build/install as >> described above, it's likely that they will be sorted out even >> faster, >> once reported here to sage-devel. >> >> Cheers, >> Georg > > --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
Georg, Thanks. My situation is a bit unique (as William fully understands). Copying the sage source from sagemath.org is not an option that I have. Our sysadmins get the source and then build it and make a built directory available to us on the system. I have to proceed from there. Victor On Aug 6, 7:02 am, gsw wrote: > On 5 Aug., 19:15, VictorMiller wrote: > > > > > > > Ok, I think I've found the problem. Perhaps this should point to the > > need for making clear and complete instructions about creating your > > own copy. > > > I found that in my local copy there was a sage script that pointed to > > the systemwide sage. When I changed that I now get my local copy. So > > perhaps the instructions should say: > > > Copy the whole directory tree. Inside the top level directory there > > is a script called sage. Edit that so that SAGE_ROOT points to your > > local copy, and use that version of sage to run sage (e.g. by making a > > symbolic link to it in one of your local directories in search order > > ahead of the system wide copy). > > > So, another question -- it seems that sage -ba didn't regerenate the > > individual doc files, since if I do something like > > > EllipticCurve?? > > > the path that it displays is in the systemwide directories. Should > > sage -ba do that? How do I regenerate these files? > > > Victor > > Hi Victor, > > a) > Just to be sure --- this sounds like the "Guess 1" from William > (second message in this thread) turned out to be 100% correct, or am I > missing something? > And if "Guess 1" was correct, how could we have phrased it better / > more understandable? > > b) > Regarding the EllipticCurve?? issue. Sorry for asking --- but did you > do "sage -ba" again, after having adressed the $SAGE_ROOT problem? > > c) > Generally speaking, the way of "copying" an existing Sage tree, and > then starting to develop, is a way rarely used. So there might be > lurking even more pitfalls yet to be discovered. > On the other hand, building Sage from source is spectacularly easy: > > - download the single tar file with all sources for the current Sage > release from sagemath.org > - unpack the tar file in the directory of your choice > - cd into the newly created "Sage root" directory (after possibly > moving and/or renaming it, if you wish so) > - type "make" (and wait a few hours) > > You then have the setup / the environment Sage is developed in, and > where certainly fewer such issues as you report are to be expected. > And *if* any problems should occur during the build/install as > described above, it's likely that they will be sorted out even faster, > once reported here to sage-devel. > > Cheers, > Georg --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
On 5 Aug., 19:15, VictorMiller wrote: > Ok, I think I've found the problem. Perhaps this should point to the > need for making clear and complete instructions about creating your > own copy. > > I found that in my local copy there was a sage script that pointed to > the systemwide sage. When I changed that I now get my local copy. So > perhaps the instructions should say: > > Copy the whole directory tree. Inside the top level directory there > is a script called sage. Edit that so that SAGE_ROOT points to your > local copy, and use that version of sage to run sage (e.g. by making a > symbolic link to it in one of your local directories in search order > ahead of the system wide copy). > > So, another question -- it seems that sage -ba didn't regerenate the > individual doc files, since if I do something like > > EllipticCurve?? > > the path that it displays is in the systemwide directories. Should > sage -ba do that? How do I regenerate these files? > > Victor > Hi Victor, a) Just to be sure --- this sounds like the "Guess 1" from William (second message in this thread) turned out to be 100% correct, or am I missing something? And if "Guess 1" was correct, how could we have phrased it better / more understandable? b) Regarding the EllipticCurve?? issue. Sorry for asking --- but did you do "sage -ba" again, after having adressed the $SAGE_ROOT problem? c) Generally speaking, the way of "copying" an existing Sage tree, and then starting to develop, is a way rarely used. So there might be lurking even more pitfalls yet to be discovered. On the other hand, building Sage from source is spectacularly easy: - download the single tar file with all sources for the current Sage release from sagemath.org - unpack the tar file in the directory of your choice - cd into the newly created "Sage root" directory (after possibly moving and/or renaming it, if you wish so) - type "make" (and wait a few hours) You then have the setup / the environment Sage is developed in, and where certainly fewer such issues as you report are to be expected. And *if* any problems should occur during the build/install as described above, it's likely that they will be sorted out even faster, once reported here to sage-devel. Cheers, Georg --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
Ok, I think I've found the problem. Perhaps this should point to the need for making clear and complete instructions about creating your own copy. I found that in my local copy there was a sage script that pointed to the systemwide sage. When I changed that I now get my local copy. So perhaps the instructions should say: Copy the whole directory tree. Inside the top level directory there is a script called sage. Edit that so that SAGE_ROOT points to your local copy, and use that version of sage to run sage (e.g. by making a symbolic link to it in one of your local directories in search order ahead of the system wide copy). So, another question -- it seems that sage -ba didn't regerenate the individual doc files, since if I do something like EllipticCurve?? the path that it displays is in the systemwide directories. Should sage -ba do that? How do I regenerate these files? Victor On Aug 5, 12:50 pm, VictorMiller wrote: > First, when I run > > mysage -sh > > and look at the environment variables involving the string SAGE, I > find they the all point to my local copy. There is a SAGE_SERVER > variable > which has the valuehttp://www.sagemath.org, but that shouldn't do > anything since the computer that I'm on is not connected to the > internet. > > as I said before, if I just start mysage, and on the command line I > type > > sys.path > > all of the values there point to my local copy. But when I run > notebook, start a new worksheet, and type sys.path > > all of the values point to the systemwide version. This also happens > if I run > > mysage -notebook foo > > with my current directory in /tmp > > At that point I'm asked to make a new password for admin, which I do. > I then see a notebook server with no worksheets defined. I start up a > new worksheet, and type sys.path -- I get the systemwide paths. I've > checked then when I do > > which sage > > it finds nothing (remember that I've called my script mysage). This > is extremely puzzling. > > Victor > > On Aug 4, 11:45 pm, Gonzalo Tornaria wrote: > > > Victor, > > > Do you have a script "sage" in your ~/bin which runs the system wide > > sage? If you run your local sage with "mysage", what happens when you > > run "sage"? What happens if you do > > > $ mysage -sh > > $ sage > > > will this run your local or the systemwide sage? > > > AFAIK, the notebook process which you run by issuing "notebook()" on > > the sage prompt doesn't execute the math itself, it only handles the > > notebook stuff. Rather, it spawns a new "sage" process, and > > communicates with it to do the math. So, it may be that for some > > reason it is spawning the system-wide install of sage rather than your > > own copy. > > > Don't recall the exact details, though, so I may be way off target. > > > Best, Gonzalo > > > On Tue, Aug 4, 2009 at 6:50 PM, VictorMiller wrote: > > > > It isn't. Systemwide SAGE is only in my path if I run a particular > > > script. I tried this in a fresh shell and checked that the systemwide > > > SAGE wasn't there. The problem was still there! > > > > Victor > > > > On Aug 4, 5:12 pm, William Stein wrote: > > >> On Tue, Aug 4, 2009 at 12:12 PM, VictorMiller > > >> wrote: > > > >> > More info. When I type > > > >> > notebook() > > > >> > after typing the banner telling me to open my web browser > > >> > it prints a path to a system files copy of sob.py (not my local > > >> > copy!) > > >> > and a deprecation warning about the md5 module. > > > >> Why don't you try editing your PATH so that the systemwide sage isn't > > >> even > > >> in your PATH? > > > >> -- William > > --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
On Aug 4, 5:57 pm, William Stein wrote: > On Tue, Aug 4, 2009 at 2:50 PM, VictorMiller wrote: > > > > > It isn't. Systemwide SAGE is only in my path if I run a particular > > script. I tried this in a fresh shell and checked that the systemwide > > SAGE wasn't there. The problem was still there! > > 1. Go to a temp directory and type > > sage -notebook foo > > to make a notebook served from a directory foo in the current tmp > directory. Does that work? NO > > 2. Try a different random port, e.g., > > sage -notebook foo port=8389 > > Does that work? NO > > 3. Grep through your install of sage for the exact path to the systemwide > sage -- what is the output? nothing. > > William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
First, when I run mysage -sh and look at the environment variables involving the string SAGE, I find they the all point to my local copy. There is a SAGE_SERVER variable which has the value http://www.sagemath.org, but that shouldn't do anything since the computer that I'm on is not connected to the internet. as I said before, if I just start mysage, and on the command line I type sys.path all of the values there point to my local copy. But when I run notebook, start a new worksheet, and type sys.path all of the values point to the systemwide version. This also happens if I run mysage -notebook foo with my current directory in /tmp At that point I'm asked to make a new password for admin, which I do. I then see a notebook server with no worksheets defined. I start up a new worksheet, and type sys.path -- I get the systemwide paths. I've checked then when I do which sage it finds nothing (remember that I've called my script mysage). This is extremely puzzling. Victor On Aug 4, 11:45 pm, Gonzalo Tornaria wrote: > Victor, > > Do you have a script "sage" in your ~/bin which runs the system wide > sage? If you run your local sage with "mysage", what happens when you > run "sage"? What happens if you do > > $ mysage -sh > $ sage > > will this run your local or the systemwide sage? > > AFAIK, the notebook process which you run by issuing "notebook()" on > the sage prompt doesn't execute the math itself, it only handles the > notebook stuff. Rather, it spawns a new "sage" process, and > communicates with it to do the math. So, it may be that for some > reason it is spawning the system-wide install of sage rather than your > own copy. > > Don't recall the exact details, though, so I may be way off target. > > Best, Gonzalo > > On Tue, Aug 4, 2009 at 6:50 PM, VictorMiller wrote: > > > It isn't. Systemwide SAGE is only in my path if I run a particular > > script. I tried this in a fresh shell and checked that the systemwide > > SAGE wasn't there. The problem was still there! > > > Victor > > > On Aug 4, 5:12 pm, William Stein wrote: > >> On Tue, Aug 4, 2009 at 12:12 PM, VictorMiller > >> wrote: > > >> > More info. When I type > > >> > notebook() > > >> > after typing the banner telling me to open my web browser > >> > it prints a path to a system files copy of sob.py (not my local > >> > copy!) > >> > and a deprecation warning about the md5 module. > > >> Why don't you try editing your PATH so that the systemwide sage isn't even > >> in your PATH? > > >> -- William > > --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
Victor, Do you have a script "sage" in your ~/bin which runs the system wide sage? If you run your local sage with "mysage", what happens when you run "sage"? What happens if you do $ mysage -sh $ sage will this run your local or the systemwide sage? AFAIK, the notebook process which you run by issuing "notebook()" on the sage prompt doesn't execute the math itself, it only handles the notebook stuff. Rather, it spawns a new "sage" process, and communicates with it to do the math. So, it may be that for some reason it is spawning the system-wide install of sage rather than your own copy. Don't recall the exact details, though, so I may be way off target. Best, Gonzalo On Tue, Aug 4, 2009 at 6:50 PM, VictorMiller wrote: > > It isn't. Systemwide SAGE is only in my path if I run a particular > script. I tried this in a fresh shell and checked that the systemwide > SAGE wasn't there. The problem was still there! > > Victor > > On Aug 4, 5:12 pm, William Stein wrote: >> On Tue, Aug 4, 2009 at 12:12 PM, VictorMiller wrote: >> >> >> >> > More info. When I type >> >> > notebook() >> >> > after typing the banner telling me to open my web browser >> > it prints a path to a system files copy of sob.py (not my local >> > copy!) >> > and a deprecation warning about the md5 module. >> >> Why don't you try editing your PATH so that the systemwide sage isn't even >> in your PATH? >> >> -- William > > > > --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
On Tue, Aug 4, 2009 at 2:50 PM, VictorMiller wrote: > > It isn't. Systemwide SAGE is only in my path if I run a particular > script. I tried this in a fresh shell and checked that the systemwide > SAGE wasn't there. The problem was still there! > 1. Go to a temp directory and type sage -notebook foo to make a notebook served from a directory foo in the current tmp directory. Does that work? 2. Try a different random port, e.g., sage -notebook foo port=8389 Does that work? 3. Grep through your install of sage for the exact path to the systemwide sage -- what is the output? William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
It isn't. Systemwide SAGE is only in my path if I run a particular script. I tried this in a fresh shell and checked that the systemwide SAGE wasn't there. The problem was still there! Victor On Aug 4, 5:12 pm, William Stein wrote: > On Tue, Aug 4, 2009 at 12:12 PM, VictorMiller wrote: > > > > > More info. When I type > > > notebook() > > > after typing the banner telling me to open my web browser > > it prints a path to a system files copy of sob.py (not my local > > copy!) > > and a deprecation warning about the md5 module. > > Why don't you try editing your PATH so that the systemwide sage isn't even > in your PATH? > > -- William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
On Tue, Aug 4, 2009 at 12:12 PM, VictorMiller wrote: > > More info. When I type > > notebook() > > after typing the banner telling me to open my web browser > it prints a path to a system files copy of sob.py (not my local > copy!) > and a deprecation warning about the md5 module. > Why don't you try editing your PATH so that the systemwide sage isn't even in your PATH? -- William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
More info. When I type notebook() after typing the banner telling me to open my web browser it prints a path to a system files copy of sob.py (not my local copy!) and a deprecation warning about the md5 module. Victor On Aug 4, 2:46 pm, gsw wrote: > Guess 2: > You need to "run" this new copy of Sage at least once, i.e. type just > "mysage" to start the Sage interpreter. > Sage recognizes that "itself" has been moved, and re-generates certain > hard-linked paths. > Have a look at (with probably $SAGE_ROOT == ~/mysage in your case) > the contents of the file "$SAGE_ROOT/local/lib/sage-current- > location.txt" --- it's silently updated by Sage whenever the Sage tree > is moved/copied. > > Guess 3: > Using "cp -p -R" did copy all the files over, but they still have only > "Read" permission (for the "user" you are), but still not "Write" > permission, so you are not allowed to modify them (by a "$SAGE_ROOT/ > sage -ba", say), although all these files are local copies now. > > Cheers, > Georg > > P.S.: > The first thing I do after installing a new Sage tree, is "$SAGE_ROOT/ > sage -clone work", in order to always have the possibility to switch > back to "vanilla" Sage by "sage -b main", and check the old behaviour. > You can always switch again to the work branch by "sage -b work". > Usually I clone more than only one work branch, i.e. "work", > "workzwo", "test" (for testing/reviewing new patches from trac), ... --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
Thanks for the suggestions. I checked -- my local copies are all writeable, and sage-current-location.txt contains my local path. As I said in the previous post, everything works ok in command line. It's just when I work from the notebook that I get pointed back at the system files. Could my ~/.sage directory be saving something that causes this? Victor On Aug 4, 2:46 pm, gsw wrote: > Guess 2: > You need to "run" this new copy of Sage at least once, i.e. type just > "mysage" to start the Sage interpreter. > Sage recognizes that "itself" has been moved, and re-generates certain > hard-linked paths. > Have a look at (with probably $SAGE_ROOT == ~/mysage in your case) > the contents of the file "$SAGE_ROOT/local/lib/sage-current- > location.txt" --- it's silently updated by Sage whenever the Sage tree > is moved/copied. > > Guess 3: > Using "cp -p -R" did copy all the files over, but they still have only > "Read" permission (for the "user" you are), but still not "Write" > permission, so you are not allowed to modify them (by a "$SAGE_ROOT/ > sage -ba", say), although all these files are local copies now. > > Cheers, > Georg > > P.S.: > The first thing I do after installing a new Sage tree, is "$SAGE_ROOT/ > sage -clone work", in order to always have the possibility to switch > back to "vanilla" Sage by "sage -b main", and check the old behaviour. > You can always switch again to the work branch by "sage -b work". > Usually I clone more than only one work branch, i.e. "work", > "workzwo", "test" (for testing/reviewing new patches from trac), ... --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
Guess 2: You need to "run" this new copy of Sage at least once, i.e. type just "mysage" to start the Sage interpreter. Sage recognizes that "itself" has been moved, and re-generates certain hard-linked paths. Have a look at (with probably $SAGE_ROOT == ~/mysage in your case) the contents of the file "$SAGE_ROOT/local/lib/sage-current- location.txt" --- it's silently updated by Sage whenever the Sage tree is moved/copied. Guess 3: Using "cp -p -R" did copy all the files over, but they still have only "Read" permission (for the "user" you are), but still not "Write" permission, so you are not allowed to modify them (by a "$SAGE_ROOT/ sage -ba", say), although all these files are local copies now. Cheers, Georg P.S.: The first thing I do after installing a new Sage tree, is "$SAGE_ROOT/ sage -clone work", in order to always have the possibility to switch back to "vanilla" Sage by "sage -b main", and check the old behaviour. You can always switch again to the work branch by "sage -b work". Usually I clone more than only one work branch, i.e. "work", "workzwo", "test" (for testing/reviewing new patches from trac), ... --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
More details. When I invoke mysage from the command line, and I type sys.path it prints paths pointing to my local branch. However, if I fire up the notebook server by notebook() start a new notebook and type sys.path it points to the system wide directory. If I type os.environ['SAGE_ROOT'] from the command line it points to my local branch but from the notebook it points to the system directory. Victor On Aug 4, 2:20 pm, William Stein wrote: > On Tue, Aug 4, 2009 at 10:40 AM, VictorMiller wrote: > > > I have a copy of SAGE 4.1 installed in our system files, and I want to > > work on changing some code. So, I copied sage and its subdirectories > > into my home directory: > > > cp -p -R sage-system-directory ~/sage > > > I also copied the sage script into my ~/bin, renaming it mysage and > > then edited the SAGE_ROOT line > > to point to ~/mysage > > > I then did a mysage -ba > > > to rebuild > > > However, when I fire up mysage, and I type > > > sys.path > > > the paths listed are still in the system directory > > > If I do something like > > > Integer?? > > > the paths listed are still in the system directory > > > I tried changing a function, then doing a sage -b, but it doesn't use > > the newly changed function > > (I put in a print statement). > > > What did I do wrong? > > Guess 1: Your sysadmin maybe edited the ROOT="" line in > SAGE_ROOT/sage to point to SAGE_ROOT. You should edit your > SAGE_ROOT/sage and change ROOT=? to the path to SAGE_ROOT in your home > directory. > > -- William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Getting started with my own branch
On Tue, Aug 4, 2009 at 10:40 AM, VictorMiller wrote: > > I have a copy of SAGE 4.1 installed in our system files, and I want to > work on changing some code. So, I copied sage and its subdirectories > into my home directory: > > cp -p -R sage-system-directory ~/sage > > I also copied the sage script into my ~/bin, renaming it mysage and > then edited the SAGE_ROOT line > to point to ~/mysage > > I then did a mysage -ba > > to rebuild > > However, when I fire up mysage, and I type > > sys.path > > the paths listed are still in the system directory > > If I do something like > > Integer?? > > the paths listed are still in the system directory > > I tried changing a function, then doing a sage -b, but it doesn't use > the newly changed function > (I put in a print statement). > > What did I do wrong? Guess 1: Your sysadmin maybe edited the ROOT="" line in SAGE_ROOT/sage to point to SAGE_ROOT. You should edit your SAGE_ROOT/sage and change ROOT=? to the path to SAGE_ROOT in your home directory. -- William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
