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 b
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 u
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,
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
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
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
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 th
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 t
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 b
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 -n
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:
>
>
>
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 y
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 cop
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 ~/.
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
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
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 scr
17 matches
Mail list logo
