I ran into this by chance and don't know what to make of it, particularly
since Sage is bundling libpng
On one machine (i7) I see:
checking for deflate in -lz... yes
checking for libpng12-config...
/mnt/hdb/sage/sage-4.4.4/local/bin/libpng12-config
checking for libpng-config...
/mnt/hdb/sage/sage
I'm probably not the typical sage user in that I use a broad array of tools
alongside and integrated into Sage. While Sage makes life easier for many
by including virtually everything anyone would need in one massive install,
where there are package replications, it becomes problematic.
Previousl
Beginning with Release 4.1.2, "sage -sh" was adjusted and now completely
strips the users environment as set in the various .*rc files.
I'm assuming there were collisions between variables needed by sage and
those the user may be setting. However, this recent change seems extreme
and makes using
I guess I should have called this "How I did it" as I doubt it has the kind
of rigor my friend mabshoff would have preferred.
The good news is that this build takes the latest code from all the repos...
and works with sage-4.1.2
http://wiki.sagemath.org/GlennTarbox/InstallingMayavi2
-glenn
--
On Sun, Oct 11, 2009 at 2:38 AM, William Stein wrote:
> On Wed, Aug 19, 2009 at 1:19 AM, Robert Bradshaw
> wrote:
> >
>
>
>
> The Sage Notebook is a Twisted application, and Twisted's "deferreds"
> might seem like a good idea for solving the above problem. However,
> they are actually *not*
Related to discussions on the notebook and extending the core Sage
infrastructure, I stumbled across a thread on the twisted mailing list
http://twistedmatrix.com/pipermail/twisted-python/2009-July/020069.html
which discusses a new introduction to asynchronous programming, why its good
/ necessar
This has become a two part question / issue:
- The use of Cython / Numpy in the notebook
- The use of Cython / Numpy on the command line
Cython itself seems to work fine with the "Hello World" example, so the core
installation is consistent with the base cython package (at least with my
adm
a bit of back and forth on the numpy list last night...
-- Forwarded message --
From: Glenn Tarbox, PhD
Date: Thu, May 14, 2009 at 1:31 AM
Subject: Re: [Numpy-discussion] numpy slices limited to 32 bit values?
To: Discussion of Numerical Python
On Wed, May 13, 2009 at 11:22
