On 10/17/07, Pierre <[EMAIL PROTECTED]> wrote: > I might be lucky with my settings, but things seem to work very simply > on my machine. I have NOTHING sage-related in my $PATH, just a > symbolic link 'sage' in /usr/bin/ that points to the actual sage > command
That is the recommended way to do things. > -- and then for standalone scripts i use > #!/usr/bin/env sage > > it works fine! Yep, that should work fine. That's for a script that is written using Sage. You can also use #!/usr/bin/env sage -python for a script that uses the Python included with Sage. > btw the decision to have nothing in my path is because i had a version > of python installed before sage (like most linux users do!) and i want > to make sure the python scripts use this version (the older one) of > python. That is a good idea. > Just in case some day a sage upgrade modifies python in such a > way that traditional python scripts will not work properly. That's actually highly likely. > I wonder what the recommendations are regarding this issue. To do exactly what you are doing. It would be totally crazy to add SAGE_ROOT/local/bin/ to one's path. It would also be fine to add SAGE_ROOT itself, since the only thing executable in there is the sage script. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-forum URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
