Don't know if this is related,
but the newest freeze symptom
seem accompanied by the message
PATH/sage/local/lib/python2.6/site-packages/sagenb-0.7.5.1-py2.6.egg/
sagenb/notebook/worksheet.py:1935: exceptions.UnicodeWarning: Unicode
equal comparison failed to convert both arguments to Unicode -
in
On Mar 28, 8:32 am, mark mcclure wrote:
> Having read the documentation on the
> server_pool option, I see that it "specifies that worksheet processes
> run as a separate user". I'm a bit unclear on exactly what that's
> supposed to mean but it makes me wonder what might happen if a large
> numbe
On Mar 27, 9:46 pm, gerhard wrote:
> The solution for me was to omit the serverpool=[...] argument
Thanks Gerhard! It is working now.
But... I'm still a bit nervous. Having read the documentation on the
server_pool option, I see that it "specifies that worksheet processes
run as a separate us
The solution for me was to omit the serverpool=[...] argument
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-s
On Mar 20, 3:15 pm, David Joyner wrote:
> > On Mar 19, 11:37 am, gerhard wrote:
> >> I tried to bring up a server on a new machine:
>
> >> compiled sage version 4.3.3 from scratch and tested it.
> >> Starting the server with
> >> notebooks_start.py
>
> Why do you want to do this instead of
> $ sa
On Sat, Mar 20, 2010 at 8:34 PM, gerhard wrote:
>> Why do you want to do this instead of
>> $ sage -notebook
>
> I want to run sage on a remote machine that I and my colleagues
> can access, potentially (but not necessarily) sharing worksheets?
Then use
$ sage -notebook
or
sage: notebook()
>
>
> Why do you want to do this instead of
> $ sage -notebook
I want to run sage on a remote machine that I and my colleagues
can access, potentially (but not necessarily) sharing worksheets?
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send
On Sat, Mar 20, 2010 at 3:12 PM, gerhard wrote:
> Has nobody encounteres this problem before?
> Any ideas of how to try and debug this?
>
> On Mar 19, 11:37 am, gerhard wrote:
>> Hi all,
>> I tried to bring up a server on a new machine:
>>
>> compiled sage version 4.3.3 from scratch and tested it
Has nobody encounteres this problem before?
Any ideas of how to try and debug this?
On Mar 19, 11:37 am, gerhard wrote:
> Hi all,
> I tried to bring up a server on a new machine:
>
> compiled sage version 4.3.3 from scratch and tested it.
> Starting the server with
> notebooks_start.py
> imp
