[sage-support] Re: import

2009-10-13 Thread georg grafendorfer
Hi Mikie, put the file with your class definitions (let's say class.py) in whatever directory (let's say /home/mikie/mydir) and add the path of this directory to the SAGE_PATH environment variable, you can do this for example by adding the line export SAGE_PATH=${SAGE_PATH}:/home/mikie/mydir to

[sage-support] Re: sage-python PYTHONPATH

2009-09-30 Thread georg grafendorfer
Thanks Burcin, Adding the path to SAGE_PATH works fine, that's the solution I was looking for, Georg On 30 Sep., 20:22, Burcin Erocal wrote: > Hi Georg, > > On Wed, 30 Sep 2009 11:07:11 -0700 (PDT) > > ggrafendorfer wrote: > > I would like to import my own library (which for example reside

[sage-support] Re: Problems with standalone python/sage scripts

2008-01-18 Thread Georg Grafendorfer
Michael, OK, i'm already a bit confused, and i don't know any more what your requesting exactly, so i will repeat some things: The file with the name ./example.sage #!/home/georg/Daten/.System/bin/sage/sage -python import sys gives me that strange mouse behaviour where the mouse pointer changes t

[sage-support] Re: exponentiation bug?

2008-01-18 Thread Georg Grafendorfer
OK, thanks, so sage-python just refers to the "sage-version" of python instead of the systems own python version and nothing else !? Georg --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send e

[sage-support] Re: Problems with standalone python/sage scripts

2008-01-18 Thread Georg Grafendorfer
Hi again, in my previous posting i had the lines #!/path/to/sage_root/local/bin sage-python #!/path/to/sage_root/local/bin sage- python instead of your request: #!/path/to/sage_root/local/bin/sage-python this gives me the same strange mouse effect as described in the original posting, whereas #

[sage-support] Re: Problems with standalone python/sage scripts

2008-01-18 Thread Georg Grafendorfer
Hi Robert, excuse me for the response delay, i did not notice your question, Does > > #!/path/to/sage_root/local/bin/sage-python > > work? no, the output is in both cases (sage -python as well as sage-python): bash: ./exp1.sage: /home/georg/Daten/.System/bin/sage/local/bin: bad interpreter: Keine

[sage-support] Re: Problems with standalone python/sage scripts

2008-01-16 Thread Georg Grafendorfer
> I thought I have seen this before and the issue was a buggy env, i.e. > > Maybe we can add some > script that does the equivalent of "sage -python", maybe "local/bin/ > sage-python" does that job, but I assume the env isn't set up > properly. #!/usr/bin/sage-python works, i mentioned this in

[sage-support] Re: Problems with standalone python/sage scripts

2008-01-15 Thread Georg Grafendorfer
Hi Robert, 1. Is this a clean, from-source build of sage-2.9.3? Yes, i tried it out on two different systems now, Athlon XP, and Core Duo, both running on Debian Etch, and both show the same behaviour 2. What is the output of /usr/bin/env for you? Mine (Intel OS X > 10.5.1) doesn't mention sage