On Mon, May 7, 2012 at 5:25 AM, <[email protected]> wrote: > On Sun, May 6, 2012 at 4:39 PM, Ralf Gommers > <[email protected]> wrote: > > > > > > On Sun, May 6, 2012 at 9:08 PM, Chris Ball <[email protected]> wrote: > >> > >> Hi, > >> > >> I'm trying to figure out how to run NumPy's tests with coverage enabled > >> (i.e. > >> numpy.test(coverage=True) ). I can run the tests successfully like this: > > > > > > This seems to have been broken somewhere along the way. If you remove the > > argument "--cover-inclusive" from line 242 in > numpy/testing/nosetester.py, > > that should fix all errors except TestNewBufferProtocol.test_roundtrip. > Not > > sure what's going on with that one. > > removing "--cover-inclusive" helped me also with statsmodels, with it > it ran all example scripts and got stuck several times, > (permanently stuck in some multiprocessing example?) > > Now coverage=True worked for the first time. > > Is it possible to make this optional or remove it from numpy? >
This should be completely be removed I think, not worth making a new keyword for. Can't imagine this being useful to a lot of people, and if it is you can still use it from the command line with "$ nosetests --with-coverage --cover-inclusive". Ralf > from a beneficiary of the nice numpy testing support outside of numpy > > Thanks for the tip, > > Josef > >
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
