Re: [Numpy-discussion] unit tests / developing numpy
![](https://secure.gravatar.com/avatar/05310d981d2f76e806e2b08fc4337164.jpg?s=120&d=mm&r=g)
Nathaniel, Pauli: Thanks for the suggestions! = runtests.py is a nice solution, but unless you also set up your PYTHONPATH and install the code you've been working on, you're going to run with whichever version of numpy you have installed normally rather than the code you've just been working on (e.g. 1.7.1 rather than 1.8dev). Unfortunately, this caused me to submit a buggy set of commits, thinking they had passed the tests. = env approach: thanks, I'll give that a try and compare it with the /tmp install approach. Can we add this to the dev workflow web pages? Graeme.
![](https://secure.gravatar.com/avatar/da3a0a1942fbdc5ee9a9b8115ac5dae7.jpg?s=120&d=mm&r=g)
= runtests.py is a nice solution, but unless you also set up your PYTHONPATH and install the code you've been working on, you're going to run with whichever version of numpy you have installed normally rather than the code you've just been working on (e.g. 1.7.1 rather
25.07.2013 17:52, Graeme B. Bell kirjoitti: [clip] than 1.8dev). No, runtests builds the code and sets PYTHONPATH accordingly. -- Pauli Virtanen
participants (2)
-
Graeme B. Bell
-
Pauli Virtanen