Thanks, William! Unfortunately, this did not solve the issue. I am still
getting the message "TypeError: Unable to start maxima".
Stan
William Stein wrote:
> On Fri, Nov 20, 2009 at 1:58 AM, Stan Schymanski wrote:
>
>> Did the upgrade still work for you?
>> Mine ended normally, but if I star
In the context of compiling sage from source ( 4.1.2 and 4.2.1 on 32bit
Debian Stable gcc-4.3.2 and 4.2.6) I find the wiki() function at the sage:
prompt raises error and no wiki -page appears.
sage: wiki()
/home/angeli/sage-4.1.2/local/lib/python2.6/site-packages/MoinMoin/user.py:9:
DeprecationW
On Fri, Nov 20, 2009 at 1:58 AM, Stan Schymanski wrote:
> Did the upgrade still work for you?
> Mine ended normally, but if I start the notebook and want to do
> something, I get the message that maxima could not be started. I'll have
> to compile from source (again).
Try forcing rebuilding of th
Did the upgrade still work for you?
Mine ended normally, but if I start the notebook and want to do
something, I get the message that maxima could not be started. I'll have
to compile from source (again). I just don't get it why the upgrade
hardly ever works form me, while I hear from others tha
Hi Stan,
On Thu, Nov 19, 2009 at 9:31 PM, Stan Schymanski wrote:
> Dear all,
>
> I compiled sage 4.2 from source on my Macbook Pro with OSX 10.4.11 and
> when I tried sage -upgrade, I was asked to enter a commit message. I
> aborted (by typing :q) and the upgrade is continuing now, but this
> doe
Dear all,
I compiled sage 4.2 from source on my Macbook Pro with OSX 10.4.11 and
when I tried sage -upgrade, I was asked to enter a commit message. I
aborted (by typing :q) and the upgrade is continuing now, but this
does not seem normal. Did anyone else experience something similar?
Thanks for y
