I've attached the hg patch that fixes the notebook problem you've
been reporting. You can apply it with
hg_sage.apply('4585.patch')
followed by "sage -br" (which will take 10 minutes)..
Or, just wait for sage-2.5.4.
On 5/24/07, William Stein <[EMAIL PROTECTED]> wrote:
> On 5/24/07, Marshall H
On 5/24/07, Marshall Hampton <[EMAIL PROTECTED]> wrote:
> Help! I was hoping to collaborate with someone using SAGE this week
> via a notebook, and I can't unless I get this fixed.
>
> Because I was getting errors as described above, where the leading /
> was missing on the path, I used a double /
Help! I was hoping to collaborate with someone using SAGE this week
via a notebook, and I can't unless I get this fixed.
Because I was getting errors as described above, where the leading /
was missing on the path, I used a double // in my path for the
notebook, i.e. a command starting out as:
n
Argh! This happened to me again, this time on a fresh 2.5.3 install.
I thought that starting from scratch might fix things.
I have the problem using a notebook with an IP address - i.e. it
hasn't happened yet on this installation on the default settings -
notebook(). Nothing will display using s
Using your libintl files solved the problem. I suspect that this is
what is also happening with some of the others (minor) problems I've
had.
Yeah, I wouldn't want to try to acquire a soon-to-be-obsolete
architecture just for development purposes either.
When I have time in the future, I'll try