On 19 Jan., 14:57, "William Stein" <[EMAIL PROTECTED]> wrote:
> I think the upshot of the entire discussion above is (or should be) to use
>
> #!/usr/bin/env sage
>
> instead of
>
> #!/usr/bin/env sage -python
>
> This assumes sage is in your path -- and indeed it should be if you want
> to write portable scripts.
>
> The second form above, e.g.,
>
> #!/usr/bin/env sage -python
>
> only works on OS X. The first form, e.g.,
>
> #!/usr/bin/env sage
>
> works on both OS X and linux. Both are equivalent in behavior on OS X.
mmhhh..., you may have a look at the sage-support thread called
"exponentiation bug?", according to this thread
sage -python refers to the python version of sage as opposed to the
system's version of python and nothing else, this sounds Ok, but from
"#!/usr/bin/env sage" i expect 2^8 to be wrapped to 2**8, or?
typing "/usr/bin/env sage" on the shell command line brings me to the
sage prompt whereas "/usr/bin/env sage-python" brings me to the python
promp...., so in OS X both commands bring you to the same prompt?
Georg
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
