> I've been using 0.80 on OS X (10.3.9) for a while with no
> problems (installed from source). I thought I'd take the
> plunge and install the latest version (again from source),
> the first time I'm trying it on the Mac with mpl's TeX
> capability. I am (still) using Apple's Python 2.3.0.
> The font in question is a PostScript Type 1 font installed by
> a music app I use (Finale). There is also an accompanying
> JazzCord.suit font suitcase. Whether these fonts are in a
> readable format or not, I would guess that mpl should be able
> to skip any font files it can't load/identify and proceed
> with what it *can* load, rather than completely aborting. Or
> perhaps this is just a symptom of another installation issue.
> Any ideas on how to proceed? Or do I just go back to 0.80?
Oops. I was debugging a font problem and commented out the
try/except part of the font manager so I could read the traceback, and
forgot to restore it. Go to line 455 on matplotlib/font_manager.py
and uncomment the except part so that it reads
font = ft2font.FT2Font(str(fpath))
warnings.warn("Could not open font file %s"%fpath)
Then remove ~/.matplotlib/ttffont.cache before running again.
> After this, further attempts to import or reload pylab give
> no errors, but there is no pylab.plot (or any other pylab
> function I've tried).
I'm not sure what this is about. Make sure you are running the
backend you think you are by running with --verbose-helpful. As
detailed in the CHANGELOG, the config file organization was recently
changed -- the matplotlibrc file now resides in ~/.matplotlib.