On Tue, Jun 19, 2007 at 05:06:42PM +0900, David Cournapeau wrote: > Robert Kern wrote: > > Stefan van der Walt wrote: > >> On Fri, Jun 15, 2007 at 03:44:37PM -0400, David M. Cooke wrote: > >>>> I meet a problem when I installed numpy. I installed numpy by the command > >>>> "python setup.py install". Then I tested it by "python -c 'import numpy; > >>>> numpy.test()'". But it doesn't work. There is an error message: > >>>> "Running from numpy source directory. > >>> ^ don't do that :) > >>> > >>> Instead, change out of the source directory, and rerun. > >> Is there any reason why we can't make that work? > > > > We have to be able to bootstrap the build process somehow. > > > wouldn't it work with the upcoming new import semantics in python 2.6 ? > The problem is that you cannot make the difference between $PWD/numpy > and $PYTHONPATH/numpy, or is this more subtle ?
I think part of the problem is that the extensions are built into some temporary directory (and I don't know of a way to query distutils for its location), which must also appear on the path for the tests to function properly. Cheers Stéfan _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
