On 10/24/06, William Stein <[EMAIL PROTECTED]> wrote:
> I have absolutely no idea. That error means that when sage tries to
> run another copy of sage, it fails at startup. I've never once not
> seen the same behavior when I tried to start SAGE from the command
> line. Ideas:
>
> (1) Try "!sage" from the "sage: " command prompt. Does it work fine?
Yes it does
>
> (2) Just do "notebook()" so it listents on localhost.
'localhost' doesn't work for me but '127.0.0.1' does.
>
> (3) From the SAGE command line, try
> sage: s = Sage()
> sage: s('2+2')
> This creates an interface to SAGE from SAGE (just like the interfaces
> from SAGE to mathematica, singular, etc.) This is a key part of how
> the notebook is implemented.
This one fails:
/home/dfdeshom/custom/sage-1.4/local/lib/python2.5/site-packages/sage/interfaces/expect.py
in __init__(self, parent, value, is_name)
650 except (TypeError, KeyboardInterrupt,
RuntimeError, ValueError), x:
651 self._session_number = -1
--> 652 raise TypeError, x
[...]
File "<stdin>", line 1, in <module>
NameError: name 'Integer' is not defined
didier
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-forum
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
