thanks for your message! i'm confused with one thing: > > -- and then for standalone scripts i use > > #!/usr/bin/env sage
> 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. i'm not 100% sure if i understand the difference between the two. My guess is: 'sage -python' uses the version of python coming with sage, and that's all; whereas 'sage' does in fact a bit more, in that it sets up the sage library somehow. Is that it ? (btw while i'm at it, thanks a lot for your work on sage, it's great. At the moment i'm writing some C++ programs and i'm using sage to help them get information from GAP and run in the right order accordingly, it's brilliantly convenient) --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
