[Numpy-discussion] [SciPy-Dev] Setting up a dev environment with conda

Luke Zoltan Kelley lzkelley at gmail.com
Sun Oct 18 23:31:46 EDT 2015

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 last):
  File "/Users/lzkelley/anaconda/envs/numpy-py27/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
  File "/Users/lzkelley/Programs/public/numpy/build/testenv/lib/python2.7/site-packages/numpy/testing/decorators.py", line 146, in skipper_func
    return f(*args, **kwargs)
  File "/Users/lzkelley/Programs/public/numpy/build/testenv/lib/python2.7/site-packages/numpy/tests/test_scripts.py", line 68, in test_f2py
    code, stdout, stderr = run_command([f2py_cmd, '-v'])
  File "/Users/lzkelley/Programs/public/numpy/build/testenv/lib/python2.7/site-packages/numpy/tests/test_scripts.py", line 48, in run_command
    proc = Popen(cmd, stdout=PIPE, stderr=PIPE)
  File "/Users/lzkelley/anaconda/envs/numpy-py27/lib/python2.7/subprocess.py", line 710, in __init__
    errread, errwrite)
  File "/Users/lzkelley/anaconda/envs/numpy-py27/lib/python2.7/subprocess.py", line 1335, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

Ran 6029 tests in 82.132s

FAILED (KNOWNFAIL=6, SKIP=10, errors=2)

f2py itself did seem to work fine from the command-line...

I did get things (seemingly) working, by cleaning the dir again, and then running:

	python setupegg.py develop --user

This built properly, and now lets me make modification to the source files and have them take effect immediately.  This is really all I need for now, but I will try to get the `./runtests.py` working for the future.  Perhaps the problem is something to do with my previous python environment installed via macports...

> On Oct 18, 2015, at 9:04 PM, Nathaniel Smith <njs at pobox.com> wrote:
> On Sun, Oct 18, 2015 at 5:02 PM, Michael Sarahan <msarahan at gmail.com> 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 folders
>> (packages) similarly to modules, and the resolution order sometimes bites
>> you.  Try cd'ing to a different folder (importantly, one NOT containing a
>> numpy folder!) and run the test command from there.
> This isn't the problem -- ./runtests.py is designed to work fine when
> run from the root of the numpy checkout.
> You might try nuking your checkout and environment and starting over
> just in case your earlier attempts left behind some broken detritus
> somewhere. 'git clean -xdf' will clear everything out of a git
> directory aside from tracked files (so make sure to add any new files
> you want to keep first!).
> -n
> -- 
> Nathaniel J. Smith -- http://vorpus.org
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20151018/99936509/attachment.html>

More information about the NumPy-Discussion mailing list