[SciPy-user] Trouble installing on OSX 10.4 Intel

David Andrews irbdavid at gmail.com
Fri Sep 15 09:00:18 CDT 2006


Hi Gaël,

Doing as you suggested produces errors with regards to libfreetype as follows:

>>> from pylab import *
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/pylab.py",
line 1, in ?
    from matplotlib.pylab import *
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/pylab.py",
line 200, in ?
    from axes import Axes, PolarAxes
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/axes.py",
line 15, in ?
    from axis import XAxis, YAxis
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/axis.py",
line 25, in ?
    from font_manager import FontProperties
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/font_manager.py",
line 39, in ?
    from matplotlib import ft2font
ImportError: Failure linking new module:
/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/ft2font.so:
Library not loaded: /usr/local/lib/libfreetype.6.dylib
  Referenced from:
/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/ft2font.so
  Reason: image not found

I think that simply copying the __init__.py from a 'working' release
of matplotlib isn't enough.  As I understand it freetype is only a
requirement in the compilation of matplotlib.

On 15/09/06, Gael Varoquaux <gael.varoquaux at normalesup.org> wrote:
>     Just grab the __init__.py out of this release and use the package
> you where using before. I think that's the simplest way to get this
> working.
>
> Gaël
>
> On Fri, Sep 15, 2006 at 02:30:13PM +0200, David Andrews wrote:
> > This is getting messy now.
> > Pulled down the latest version of matplotlib (0.87.5), and installed
> > it.  Now experiencing issues due to incompatibility between this
> > latest version of matplotlib and the version of numpy in the
> > superpack:
>
> > >>> from pylab import *
> > RuntimeError: module compiled against version 1000002 of C-API but
> > this version of numpy is 1000000
>
> > The import of the numpy version of the nxutils module,
> > _nsnxutils, failed.  This is is either because numpy was
> > unavailable when matplotlib was compiled, because a dependency of
> > _nsnxutils could not be satisfied, or because the build flag for
> > this module was turned off in setup.py.  If it appears that
> > _nsnxutils was not built, make sure you have a working copy of
> > numpy and then re-install matplotlib. Otherwise, the following
> > traceback gives more details:
>
> > Traceback (most recent call last):
> >   File "<stdin>", line 1, in ?
> >   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/pylab.py",
> > line 1, in ?
> >     from matplotlib.pylab import *
> >   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/pylab.py",
> > line 198, in ?
> >     import mlab  #so I can override hist, psd, etc...
> >   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/mlab.py",
> > line 64, in ?
> >     import nxutils
> >   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/nxutils.py",
> > line 17, in ?
> >     from matplotlib._ns_nxutils import *
> > ImportError: numpy.core.multiarray failed to import
>
> > Scipy and numpy can be imported okay.  This is sounding more like a
> > matplotlib issue than a numpy/scipy issue isn't it?  At any rate I
> > think the packages in the superpack need to be updated and tested
> > together.
>
> > Cheers,
>
> > Dave
>
> > On 15/09/06, Gael Varoquaux <gael.varoquaux at normalesup.org> wrote:
> > > On Thu, Sep 14, 2006 at 11:30:59PM +0200, David Andrews wrote:
> > > > The stuff in the .mpkg should remain after the install, yeah.  If its
> > > > not there now, it never was :)  Looks like it's been missed out
> > > > somewhere a long the way...
>
> > >     On the matplotlib-dev list there has been some mentions of a
> > > forgotten __init__.py in the latest release. This has been fixed, but
> > > maybe not in the package you are using. You can grab this __init__.py
> > > from the .tar.gz from the matplotlib site, and this should fix your
> > > problem (I think).
>
> > > Gaël
> > > _______________________________________________
> > > SciPy-user mailing list
> > > SciPy-user at scipy.org
> > > http://projects.scipy.org/mailman/listinfo/scipy-user
>
> > _______________________________________________
> > SciPy-user mailing list
> > SciPy-user at scipy.org
> > http://projects.scipy.org/mailman/listinfo/scipy-user
> _______________________________________________
> SciPy-user mailing list
> SciPy-user at scipy.org
> http://projects.scipy.org/mailman/listinfo/scipy-user
>


More information about the SciPy-user mailing list