I feel your pain on the issue of eggs...
- Is there some way to name the eggs to disambiguate between 32-bit
Python 2.7 (which works on all versions of Mac OS X) and 64-bit Python
2.7 (which only works on 10.6) that is compatible with easy_install?
In the past if the eggs had strange names easy_install misbehaved.
When I built the readline package on the Mac, I ran into similar
issues. To keep things simple (or so I thought), I built one universal
egg. On Leopard with Apple Python 2.5 (see
http://pypi.python.org/pypi/readline/2.5.1) and the setuptools at the
time (May 2008), the egg was named *-fat.egg. Since there is no
architecture called "fat", easy_install refused to select it for
installation. So I renamed it to the explicit architectures
(*-i386.egg, *-ppc.egg, *-ppc64.egg, *-x86_64.egg), but this was
another saga, since PyPI refused to upload identical files with
different names. I then tweaked each egg slightly to bypass this...
Very silly, as you can see.
The latest version of the readline package
(http://pypi.python.org/pypi/readline) has an egg for Leopard and Snow
Leopard built against the default Apple Python on each system. On Snow
Leopard and Python 2.6, the egg is now called *-universal.egg and
seems to work with the latest easy_install. To avoid repeating the
silly tweaking of eggs, I renamed the Leopard *-fat.egg to *-i386.egg
only, as that is pretty much the dominant architecture which will keep
most easy_install users happy (70% of the downloads of the 2.5.1
Leopard version with four eggs picked the i386 egg).
To get back to your question, I would venture something like
matplotlib-1.0.1-py2.7-macosx-10.6-x86_64.egg (ditto for the ppc
So my recommendation is not to Python 2.5 on a Mac.
I have been running matplotlib on Apple Python 2.5 on Leopard mostly
with the TkAgg backend (on Apple Tk) for a few years now - maybe it's
time to upgrade