Thanks -- I will try that.
I'm finding, as I work through all of this, that some of the Python
add-on packages (while excellent) are not trivial to install.
T. Davis
On Dec 10, 7:17 pm, William Stein wrote:
> On Thu, Dec 10, 2009 at 4:10 PM, TDavis wrote:
> > Hi, this is a f
all went
fine. I think the same thing would probably work inside sage if one
is willing to do some hand editing.
In my opinion, the problem is the inflexible installation process for
'matplotlib'. Couldn't the python setup scripts be given at least one
additional option that woul
I have set TkAgg as the matplotlib backend in my matplotlibrc resource
file. I continue to have errors when I try to 'import pylab'. To
make certain it was not a Tkinter issue, I tested Tkinter and re-
installed matplotlib via "./sage -f matplotlib-0.99.1.p2"
I'm running SLED 10.2 and built sage
All:
I reported an issue a few days ago in which sage's python 2.6 was not
properly configured for tcl/tk. My native "stand-alone" version of
python 2.6 (outside of sage) was just fine,though.
I've resolved the issue, thanks to a suggestion from this discussion
group.
I went to my system-wide i
Thanks -- I'll give that a try.
T. Davis
On Dec 1, 7:04 pm, Timothy Davis wrote:
> Dear Sage-support:
>
> I am trying to build Sage 4.2.1 from source on a Linux machine running SUSE
> Linux Enterprise Server 10 (x86_64).
>
> The build proceeds to the end, but I have a persistent problem with the
