Weighing in on the Mac build issue:
- The only GUI backends worth building on Mac OS X are TkAgg and the
native macosx one, in my humble opinion. Sticking to them will prevent
the kind of pain Kynn described. These backends are autodetected by
default during the build process and you only land in trouble if you
explicitly enable the rest. My suggestion is therefore to do the
default "python setup.py install".
- I have been successfully using the Apple "system" Python since Mac
OS 10.5 to run numpy/scipy/matplotlib/ipython and never encountered
any major build or usage problems. I agree that Mac OS 10.4 and
earlier needed a Python reinstallation, but do not see why it is
currently still a strong requirement. Ben, do you know off-hand what
issues numpy has been having with Apple Python?
As improved documentation I can contribute (yet another :-)) tutorial
for building and installing matplotlib and friends on a clean Mac OS
10.6 system, with a minimum of downloaded packages and using the
standard system stuff as far as possible. I fine-tuned the
instructions on several iMacs at work. I will just check that it still
works with the latest packages.
Date: Thu, 18 Nov 2010 16:57:10 -0600
From: Benjamin Root <ben.root@...553...>
There are a variety of issues depending on your Mac system that needs to be
sorted out to determine the best way to go about installing everything. The
particular sticking point is that Apple supplied their own interperater
rather than the standard python interpreater. Unfortunately, this causes
problems with numpy (and thus matplotlib).