[SciPy-dev] CVS updates complete

eric eric at scipy.org
Wed Apr 3 14:48:39 CST 2002


----- Original Message -----
From: <pearu at scipy.org>
To: <scipy-dev at scipy.org>
Sent: Wednesday, April 03, 2002 4:24 PM
Subject: Re: [SciPy-dev] CVS updates complete


>
>
> 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.

Ok.  I'll try using this.

>
> 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:41
8: 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

These are errors that are caught and warned about.  I think all is working fine.

So is Python2.2 passing all tests for you?  Travis O. is having some problems on
Mandrake as we speak with the underflow problem reported recently on the Numeric
lists.

Also, my last tests on windows with 2.2b1 (I think) caused seg-faults.  We're
both upgrading to 2.2.1c2 to see if that helps.

eric


>
>
> Pearu
>
> _______________________________________________
> Scipy-dev mailing list
> Scipy-dev at scipy.net
> http://www.scipy.net/mailman/listinfo/scipy-dev
>





More information about the Scipy-dev mailing list