Thanks for the help Nathaniel --- but building via `./runtests.py` is failing
in the same way. Hopefully Numpy-discussion can help me out.
I'm able to build using `python setup.py build_ext --inplace` but both trying
to run `python setup.py install` or `./runtests.py` leads to the following
Hi Luke,
Could you check if you have "/Users/lzkelley/Programs/public/numpy/ in
your PYTHONPATH?
I would also suggest you add a print(np) line before the crash in
nosetester.py. I got something like this (which didn't crash):
If you see something not starting with 'numpy/build', then it is
Thanks Yu,
There was nothing in my PYTHONPATH at first, and adding my numpy directory
('/Users/lzkelley/Programs/public/numpy') didn't help (same error). In both
cases, adding 'print(np)' yields:
> On Oct 18, 2015, at 7:22 PM, Feng Yu wrote:
>
> Hi Luke,
>
> Could
Running tests in the folder might be causing your problem. If it's trying
to import numpy, and numpy is a folder in your current folder, sometimes
you see errors like this. The confusion is that Python treats folders
(packages) similarly to modules, and the resolution order sometimes bites
you.
On Sun, Oct 18, 2015 at 5:02 PM, Michael Sarahan wrote:
> Running tests in the folder might be causing your problem. If it's trying
> to import numpy, and numpy is a folder in your current folder, sometimes you
> see errors like this. The confusion is that Python treats
I tried cleaning the git dir, and trying again. It still didn't work giving me
the report:
==
ERROR: test_scripts.test_f2py
--
Traceback (most recent call
Hi Luke,
For day-to-day development and testing of numpy, I don't bother with
either inplace builds *or* installing it -- I just use the magical
"runtests.py" script that you'll find in the root of your git
checkout.
E.g., to build and then test the (possibly modified) source in your
current