![](https://secure.gravatar.com/avatar/e9446ff18bd813fdcaa548b090f79427.jpg?s=120&d=mm&r=g)
Hi, I'm a little lost here - i've d/led and installed everything in the scipy superpack, yet i am still unable to import certain components of scipy and matplotlib / pylab. The only thing that does appear to be fully installed is numpy, which i guess is a start. So here is what I get when i try 'from scipy import *': Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/__init__.py", line 5, in ? from linsolve import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/linsolve.py", line 1, in ? from scipy.sparse import isspmatrix_csc, isspmatrix_csr, isspmatrix, spdiags File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/__init__.py", line 5, in ? from sparse import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparse.py", line 12, in ? import sparsetools ImportError: Failure linking new module: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so: Library not loaded: /usr/local/lib/libgfortran.1.dylib Referenced from: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so Reason: image not found And with '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 * ImportError: No module named matplotlib.pylab So any suggestions? I previously had a working install of matplotlib/pylab and numpy, if that suggest anything to you? I think sticking a readme file in the superpack might be a good idea. Cheers, Dave
![](https://secure.gravatar.com/avatar/dcf19f8904be1850ac17837400444254.jpg?s=120&d=mm&r=g)
Strange, I used the superpack on a Mac Pro and everything installed fine. Did you install the pre-compiled gfortran for intel compilers on your macine first? Just a thought. I think they're included in the superpack. Conor On 9/14/06, David Andrews <irbdavid@gmail.com> wrote:
Hi,
I'm a little lost here - i've d/led and installed everything in the scipy superpack, yet i am still unable to import certain components of scipy and matplotlib / pylab. The only thing that does appear to be fully installed is numpy, which i guess is a start.
So here is what I get when i try 'from scipy import *':
Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/__init__.py", line 5, in ? from linsolve import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/linsolve.py", line 1, in ? from scipy.sparse import isspmatrix_csc, isspmatrix_csr, isspmatrix, spdiags File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/__init__.py", line 5, in ? from sparse import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparse.py", line 12, in ? import sparsetools ImportError: Failure linking new module: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so: Library not loaded: /usr/local/lib/libgfortran.1.dylib Referenced from: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so Reason: image not found
And with '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 * ImportError: No module named matplotlib.pylab
So any suggestions?
I previously had a working install of matplotlib/pylab and numpy, if that suggest anything to you?
I think sticking a readme file in the superpack might be a good idea.
Cheers,
Dave _______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
![](https://secure.gravatar.com/avatar/e9446ff18bd813fdcaa548b090f79427.jpg?s=120&d=mm&r=g)
Part of the problem would appear to have been me borking the install of gfortran - reinstalling the binaries for it has fixed the scipy issue. The issue with pylab not working persists - should this superpack provide a full working install of matplotlib/pylab? I remember a while back having to fight with backends for it, though that doesnt appear to have a bearing on the current problem i'm having. Thanks for the quick reply Conor, Cheers, Dave On 14/09/06, Conor Robinson <conor.robinson@gmail.com> wrote:
Strange, I used the superpack on a Mac Pro and everything installed fine. Did you install the pre-compiled gfortran for intel compilers on your macine first? Just a thought. I think they're included in the superpack.
Conor
On 9/14/06, David Andrews <irbdavid@gmail.com> wrote:
Hi,
I'm a little lost here - i've d/led and installed everything in the scipy superpack, yet i am still unable to import certain components of scipy and matplotlib / pylab. The only thing that does appear to be fully installed is numpy, which i guess is a start.
So here is what I get when i try 'from scipy import *':
Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/__init__.py", line 5, in ? from linsolve import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/linsolve.py", line 1, in ? from scipy.sparse import isspmatrix_csc, isspmatrix_csr, isspmatrix, spdiags File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/__init__.py", line 5, in ? from sparse import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparse.py", line 12, in ? import sparsetools ImportError: Failure linking new module: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so: Library not loaded: /usr/local/lib/libgfortran.1.dylib Referenced from: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so Reason: image not found
And with '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 * ImportError: No module named matplotlib.pylab
So any suggestions?
I previously had a working install of matplotlib/pylab and numpy, if that suggest anything to you?
I think sticking a readme file in the superpack might be a good idea.
Cheers,
Dave _______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
![](https://secure.gravatar.com/avatar/cd57f26a7ba7beb7486c092c6a44f70f.jpg?s=120&d=mm&r=g)
I got the "No module named matplotlib.pylab" error. I'd installed from the windows installer, and after some considerable head-scratching, figured out that the __init__.py file was missing from the matplotlib module ... so Python didn't recognize it as a module. I found the file in the unzipped .egg, copied it to matplotlib, and everybody seems to be happy. john David Andrews wrote:
Part of the problem would appear to have been me borking the install of gfortran - reinstalling the binaries for it has fixed the scipy issue. The issue with pylab not working persists - should this superpack provide a full working install of matplotlib/pylab? I remember a while back having to fight with backends for it, though that doesnt appear to have a bearing on the current problem i'm having.
Thanks for the quick reply Conor,
Cheers,
Dave
"/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/pylab.py", line 1, in ? from matplotlib.pylab import * ImportError: No module named matplotlib.pylab
So any suggestions?
![](https://secure.gravatar.com/avatar/e9446ff18bd813fdcaa548b090f79427.jpg?s=120&d=mm&r=g)
Hi John, I'm looking at the contents of the installer archive, i don't seem to see an __init_.py in the matplotlib directory, though they do appear for sub directories of the matplotlib directory (numericx/ etc) - perhaps its physically missing from the installer? Conor; as John has noted the lack of an __init__.py in the module would render it invisible to python, causing the problem we're seein Cheers, DAve On 14/09/06, John Hassler <hasslerjc@adelphia.net> wrote:
I got the "No module named matplotlib.pylab" error. I'd installed from the windows installer, and after some considerable head-scratching, figured out that the __init__.py file was missing from the matplotlib module ... so Python didn't recognize it as a module. I found the file in the unzipped .egg, copied it to matplotlib, and everybody seems to be happy. john
David Andrews wrote:
Part of the problem would appear to have been me borking the install of gfortran - reinstalling the binaries for it has fixed the scipy issue. The issue with pylab not working persists - should this superpack provide a full working install of matplotlib/pylab? I remember a while back having to fight with backends for it, though that doesnt appear to have a bearing on the current problem i'm having.
Thanks for the quick reply Conor,
Cheers,
Dave
"/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/pylab.py", line 1, in ? from matplotlib.pylab import * ImportError: No module named matplotlib.pylab
So any suggestions?
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
![](https://secure.gravatar.com/avatar/dcf19f8904be1850ac17837400444254.jpg?s=120&d=mm&r=g)
David, I just tried "from pylab import *" and got the same error. It looks to me that python is not understanding matplotlib. as the dir for pylab.py I tried copying the actual pylab into the python2.4 dir or site-packages dir (replace pylab.py int version) so it finds it first before the current pylab init and then it can't find cm.py and im assuming the rest of the modules. I've currently been unsing gnuplot.py so I never bothered testing this, but it would be nice to make it work. Fairly sure this is a dir issue. Any ideas? Conor On 9/14/06, David Andrews <irbdavid@gmail.com> wrote:
Part of the problem would appear to have been me borking the install of gfortran - reinstalling the binaries for it has fixed the scipy issue. The issue with pylab not working persists - should this superpack provide a full working install of matplotlib/pylab? I remember a while back having to fight with backends for it, though that doesnt appear to have a bearing on the current problem i'm having.
Thanks for the quick reply Conor,
Cheers,
Dave
On 14/09/06, Conor Robinson <conor.robinson@gmail.com> wrote:
Strange, I used the superpack on a Mac Pro and everything installed fine. Did you install the pre-compiled gfortran for intel compilers on your macine first? Just a thought. I think they're included in the superpack.
Conor
On 9/14/06, David Andrews <irbdavid@gmail.com> wrote:
Hi,
I'm a little lost here - i've d/led and installed everything in the scipy superpack, yet i am still unable to import certain components of scipy and matplotlib / pylab. The only thing that does appear to be fully installed is numpy, which i guess is a start.
So here is what I get when i try 'from scipy import *':
Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/__init__.py", line 5, in ? from linsolve import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/linsolve.py", line 1, in ? from scipy.sparse import isspmatrix_csc, isspmatrix_csr, isspmatrix, spdiags File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/__init__.py", line 5, in ? from sparse import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparse.py", line 12, in ? import sparsetools ImportError: Failure linking new module: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so: Library not loaded: /usr/local/lib/libgfortran.1.dylib Referenced from: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so Reason: image not found
And with '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 * ImportError: No module named matplotlib.pylab
So any suggestions?
I previously had a working install of matplotlib/pylab and numpy, if that suggest anything to you?
I think sticking a readme file in the superpack might be a good idea.
Cheers,
Dave _______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
![](https://secure.gravatar.com/avatar/dcf19f8904be1850ac17837400444254.jpg?s=120&d=mm&r=g)
I looked in the unzipped egg and didn't see the init, is it left in the folder after the install? thanks On 9/14/06, Conor Robinson <conor.robinson@gmail.com> wrote:
David,
I just tried "from pylab import *" and got the same error. It looks to me that python is not understanding matplotlib. as the dir for pylab.py I tried copying the actual pylab into the python2.4 dir or site-packages dir (replace pylab.py int version) so it finds it first before the current pylab init and then it can't find cm.py and im assuming the rest of the modules. I've currently been unsing gnuplot.py so I never bothered testing this, but it would be nice to make it work. Fairly sure this is a dir issue. Any ideas?
Conor
On 9/14/06, David Andrews <irbdavid@gmail.com> wrote:
Part of the problem would appear to have been me borking the install of gfortran - reinstalling the binaries for it has fixed the scipy issue. The issue with pylab not working persists - should this superpack provide a full working install of matplotlib/pylab? I remember a while back having to fight with backends for it, though that doesnt appear to have a bearing on the current problem i'm having.
Thanks for the quick reply Conor,
Cheers,
Dave
On 14/09/06, Conor Robinson <conor.robinson@gmail.com> wrote:
Strange, I used the superpack on a Mac Pro and everything installed fine. Did you install the pre-compiled gfortran for intel compilers on your macine first? Just a thought. I think they're included in the superpack.
Conor
On 9/14/06, David Andrews <irbdavid@gmail.com> wrote:
Hi,
I'm a little lost here - i've d/led and installed everything in the scipy superpack, yet i am still unable to import certain components of scipy and matplotlib / pylab. The only thing that does appear to be fully installed is numpy, which i guess is a start.
So here is what I get when i try 'from scipy import *':
Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/__init__.py", line 5, in ? from linsolve import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/linsolve.py", line 1, in ? from scipy.sparse import isspmatrix_csc, isspmatrix_csr, isspmatrix, spdiags File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/__init__.py", line 5, in ? from sparse import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparse.py", line 12, in ? import sparsetools ImportError: Failure linking new module: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so: Library not loaded: /usr/local/lib/libgfortran.1.dylib Referenced from: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so Reason: image not found
And with '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 * ImportError: No module named matplotlib.pylab
So any suggestions?
I previously had a working install of matplotlib/pylab and numpy, if that suggest anything to you?
I think sticking a readme file in the superpack might be a good idea.
Cheers,
Dave _______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
![](https://secure.gravatar.com/avatar/e9446ff18bd813fdcaa548b090f79427.jpg?s=120&d=mm&r=g)
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... Cheers, Dave On 14/09/06, Conor Robinson <conor.robinson@gmail.com> wrote:
I looked in the unzipped egg and didn't see the init, is it left in the folder after the install?
thanks
On 9/14/06, Conor Robinson <conor.robinson@gmail.com> wrote:
David,
I just tried "from pylab import *" and got the same error. It looks to me that python is not understanding matplotlib. as the dir for pylab.py I tried copying the actual pylab into the python2.4 dir or site-packages dir (replace pylab.py int version) so it finds it first before the current pylab init and then it can't find cm.py and im assuming the rest of the modules. I've currently been unsing gnuplot.py so I never bothered testing this, but it would be nice to make it work. Fairly sure this is a dir issue. Any ideas?
Conor
On 9/14/06, David Andrews <irbdavid@gmail.com> wrote:
Part of the problem would appear to have been me borking the install of gfortran - reinstalling the binaries for it has fixed the scipy issue. The issue with pylab not working persists - should this superpack provide a full working install of matplotlib/pylab? I remember a while back having to fight with backends for it, though that doesnt appear to have a bearing on the current problem i'm having.
Thanks for the quick reply Conor,
Cheers,
Dave
On 14/09/06, Conor Robinson <conor.robinson@gmail.com> wrote:
Strange, I used the superpack on a Mac Pro and everything installed fine. Did you install the pre-compiled gfortran for intel compilers on your macine first? Just a thought. I think they're included in the superpack.
Conor
On 9/14/06, David Andrews <irbdavid@gmail.com> wrote:
Hi,
I'm a little lost here - i've d/led and installed everything in the scipy superpack, yet i am still unable to import certain components of scipy and matplotlib / pylab. The only thing that does appear to be fully installed is numpy, which i guess is a start.
So here is what I get when i try 'from scipy import *':
Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/__init__.py", line 5, in ? from linsolve import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/linsolve/linsolve.py", line 1, in ? from scipy.sparse import isspmatrix_csc, isspmatrix_csr, isspmatrix, spdiags File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/__init__.py", line 5, in ? from sparse import * File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparse.py", line 12, in ? import sparsetools ImportError: Failure linking new module: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so: Library not loaded: /usr/local/lib/libgfortran.1.dylib Referenced from: /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/scipy/sparse/sparsetools.so Reason: image not found
And with '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 * ImportError: No module named matplotlib.pylab
So any suggestions?
I previously had a working install of matplotlib/pylab and numpy, if that suggest anything to you?
I think sticking a readme file in the superpack might be a good idea.
Cheers,
Dave _______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
![](https://secure.gravatar.com/avatar/5c9fb379c4e97b58960d74dcbfc5dee5.jpg?s=120&d=mm&r=g)
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
![](https://secure.gravatar.com/avatar/e9446ff18bd813fdcaa548b090f79427.jpg?s=120&d=mm&r=g)
from pylab import * RuntimeError: module compiled against version 1000002 of C-API but
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: 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@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@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
![](https://secure.gravatar.com/avatar/5c9fb379c4e97b58960d74dcbfc5dee5.jpg?s=120&d=mm&r=g)
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@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@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
![](https://secure.gravatar.com/avatar/e9446ff18bd813fdcaa548b090f79427.jpg?s=120&d=mm&r=g)
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",
Hi Gaël, Doing as you suggested produces errors with regards to libfreetype as follows: 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@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@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@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
![](https://secure.gravatar.com/avatar/e9446ff18bd813fdcaa548b090f79427.jpg?s=120&d=mm&r=g)
Currently the superpack contains numpy 1.1.2880, though the numpy sourceforge site lists only 0.9.8 or 1.0b5 as current releases of numpy - perhaps this is causing the compatibility issues? On 15/09/06, David Andrews <irbdavid@gmail.com> 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@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@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user
participants (4)
-
Conor Robinson
-
David Andrews
-
Gael Varoquaux
-
John Hassler