Hi, I am trying to install from cvs, but am getting error
> messages that the numerix module is missing. It is not
> listed on the "browse cvs repository" page at sourceforge
> either.
Try getting a new CVS checkout in a clean directory and rm -rf
site-packages/matplotlib before rebuilding. The numerix module does
exist in CVS:
matplotlib download | SourceForge.net
The numerix code was reorganized in 0.71 so if you are using an older
version that can cause problems. The first line of defense when
confronting a matplotlib bug is
> sudo rm -rf build /usr/local/lib/python2.3/site-packages/matplotib
> sudo python setup.py install
distutils keeps old code around in the build directory. If for
example you have somemod.so from an older mpl version, and then we
refactor to use somemod.py which conditionally imports _na_somemod.so
or _nc_somemod.so depending on your numerix setting, the old
somemod.so will be installed from your build dir into site-packages
alongside somemod.py but the old *.so will be imported rather than the
new *.py. This has caused us lots of problems - I don't think a
'python setup.py clean' will solve every problem, but flushing the
build directory and site-packages/matplotlib before a new install has
cured lots of bugs.
Or else sourceforge CVS is whacked, which would not bee too
surprising.
JDH
My mistake. I thought I had cleared the build and site-packages/mpl directory,
but I guess I overlooked something. I did a new cvs co and numerix is back.
Thanks.
···
On Friday 25 February 2005 11:33 am, John Hunter wrote:
> Hi, I am trying to install from cvs, but am getting error
> messages that the numerix module is missing. It is not
> listed on the "browse cvs repository" page at sourceforge
> either.
Try getting a new CVS checkout in a clean directory and rm -rf
site-packages/matplotlib before rebuilding. The numerix module does
exist in CVS:
matplotlib download | SourceForge.net
numerix/
The numerix code was reorganized in 0.71 so if you are using an older
version that can cause problems. The first line of defense when
confronting a matplotlib bug is
> sudo rm -rf build /usr/local/lib/python2.3/site-packages/matplotib
> sudo python setup.py install
distutils keeps old code around in the build directory. If for
example you have somemod.so from an older mpl version, and then we
refactor to use somemod.py which conditionally imports _na_somemod.so
or _nc_somemod.so depending on your numerix setting, the old
somemod.so will be installed from your build dir into site-packages
alongside somemod.py but the old *.so will be imported rather than the
new *.py. This has caused us lots of problems - I don't think a
'python setup.py clean' will solve every problem, but flushing the
build directory and site-packages/matplotlib before a new install has
cured lots of bugs.
Or else sourceforge CVS is whacked, which would not bee too
surprising.
--
Darren