On Thu, Aug 13, 2015 at 10:00 AM, Sebastian Berg <sebast...@sipsolutions.net > wrote:
> On Do, 2015-08-13 at 15:52 +0000, Anne Archibald wrote: > > Hi, > > > > > > What is a sensible way to work on (modify, compile, and test) numpy? > > > > > > There is documentation about "contributing to numpy" at: > > http://docs.scipy.org/doc/numpy-dev/dev/index.html > > > > and: > > > http://docs.scipy.org/doc/numpy-dev/dev/gitwash/development_workflow.html > > > > but these are entirely focused on using git. I have no problem with > > that aspect. It is building and testing that I am looking for the > > Right Way to do. > > > > > > My current approach is to build an empty virtualenv, pip install nose, > > and from the numpy root directory do "python setup.py build_ext > > --inplace" and "python -c 'import numpy; numpy.test()'". This works, > > for my stock system python, though I get a lot of weird messages > > suggesting distutils problems (for example "python setup.py develop", > > although suggested by setup.py itself, claims that "develop" is not a > > command). But I don't know how (for example) to test with python3 > > without starting from a separate clean source tree. > > > > We have the `runtests.py` script which will do exactly this (don't think > it gives lots of weird warnings normally). I think that is the only real > tip I can give. > +1 for `runtests.py`. Do `python runtests.py --help` to get started. If you want another python, say 3.5, `python3.5 runtests.py`. Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion