On Mon, Sep 28, 2009 at 4:47 AM, Dr. David Kirkby
david.kir...@onetel.net wrote:
William Stein wrote:
Hi,
I spent several hours yesterday trying to get matplotlib for Sage to
work on OS X 10.6. On my laptop everything works perfectly, but on
another test machine (bsd.math) the workaround
I forgot a detail: you have to use a script to edit the commandline
arguments to pass to gcc:
#!/bin/sh
y=
for x in $*
do
case $x
in
-xcode*)
echo skip $x
;;
*)
y=$y $x
;;
esac
done
gcc $y
and then do
This is a very long-standing bug in distutils:
http://bugs.python.org/issue1222585
While distutils distinguishes between C and C++ for *linking*, it does
not do so for *compiling*. This doesn't matter for gcc and msvc (which
are arguably the two most popular compilers for Python), but
Michael Droettboom wrote:
This is a very long-standing bug in distutils:
http://bugs.python.org/issue1222585
While distutils distinguishes between C and C++ for *linking*, it does
not do so for *compiling*. This doesn't matter for gcc and msvc (which
are arguably the two most popular
On Mon, Sep 28, 2009 at 4:54 AM, John Hunter jdh2...@gmail.com wrote:
On Mon, Sep 28, 2009 at 4:47 AM, Dr. David Kirkby
david.kir...@onetel.net wrote:
William Stein wrote:
Hi,
I spent several hours yesterday trying to get matplotlib for Sage to
work on OS X 10.6. On my laptop everything
On Mon, Sep 28, 2009 at 11:14 AM, John Hunter jdh2...@gmail.com wrote:
But even simple tests are failing with::
jdh2...@bsd:~ LD_LIBRARY_PATH=~/devtest/lib/
PYTHONPATH=~/devtest/lib/python2.6/site-packages/ /usr/bin/python -c
'import matplotlib; matplotlib.use(Agg); from matplotlib.pyplot