[SciPy-dev] CVS updates complete

pearu at scipy.org pearu at scipy.org
Wed Apr 3 15:24:59 CST 2002


On Wed, 3 Apr 2002, eric wrote:

> This brings up a good point though.  Testing is a little difficult because you
> have to do a python setup.py install to get everything in the correct location.
> Should we alter scipy_distutils to copy files into the build directory when
> "python setup.py build" is used?  That way you can just cd to the build/lib.xxx
> directory and try things out without installing.

In general it makes sense not to copy data files when building.
I think we do not need to alter scipy_distutils for testing. Doing, for
example

  setup.py install --prefix=/tmp  
  cd /tmp/lib/python2.2/site-packages
  python -c 'import scipy;scipy.test()'

should give a work around for this problem.

BTW, weave tests all pass with Python 2.2 and gcc version 2.95.4.
Though I still get

/home/users/pearu/.python22_compiled/sc_9a25bc84add18fe6c75501f6b01bd84e1.cpp: In
function `struct PyObject * compiled_func(PyObject *, PyObject *)':
/home/users/pearu/.python22_compiled/sc_9a25bc84add18fe6c75501f6b01bd84e1.cpp:418: no
match for `Py::String & < int'
/home/users/pearu/src_cvs/scipy/build/lib.linux-i686-2.2/scipy/weave/CXX/Objects.hxx:390: candidates
are: bool Py::Object::operator <(const Py::Object &) const
/home/users/pearu/src_cvs/scipy/build/lib.linux-i686-2.2/scipy/weave/CXX/Objects.hxx:1433:                 bool
Py::operator <(const Py::SeqBase<Py::Object>::const_iterator &, const
Py::SeqBase<Py::Object>::const_iterator &)
/home/users/pearu/src_cvs/scipy/build/lib.linux-i686-2.2/scipy/weave/CXX/Objects.hxx:1426:                 bool
Py::operator <(const Py::SeqBase<Py::Object>::iterator &, const
Py::SeqBase<Py::Object>::iterator &)
.warning: specified build_dir '_bad_path_' does not exist or is or is not
writable. Trying default locations


Pearu




More information about the Scipy-dev mailing list