You should commit your changes to a branch and push to a bitbucket repo so we can see your changes. Our test runner compiles part of PyPy and calls the tests using that partial interpreter (unless run with -A), when you call import numpy inside a test you are using micronumpy. You should not try to stop in a debugger in the test code itself (app level), rather print or set_trace inside micronumpy code (interpreter level). Matti
> On 20 May 2016, at 10:18 PM, Eli Stevens (Gmail) <wickedg...@gmail.com> wrote: > > I understand that the tests are in the test directory, but the issue > I'm currently trying to figure out is that when I invoke either of: > > /usr/bin/python test_all.py test_all.py > module/micronumpy/test/test_flagsobj.py > > /usr/bin/python pytest.py > pypy/module/micronumpy/test/test_flagsobj.py (a directory level up) > > With any of system cpython, venv cpython, venv pypy, etc. then the > changes that I've made locally to micronumpy aren't used, since inside > of the tests "import numpy" grabs the numpy from whatever interpreter > the tests were invoked with. > > I'm sure there's something simple that I'm missing about the > environment that's needed to make this work, but I haven't figured it > out yet. Do I need to be doing something with the PYTHONPATH prior to > running the tests? > > Cheers, > Eli > > >> _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
