On 1/11/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Keith Goodman wrote:
> > I see a lot of 'No test file found' warnings when running
> > numpy.test(). What does that mean?
>
> The test collector tries to find a test module for every actual module. So
> numpy/dual.py would correspond to numpy/tes
Keith Goodman wrote:
> I see a lot of 'No test file found' warnings when running
> numpy.test(). What does that mean?
The test collector tries to find a test module for every actual module. So
numpy/dual.py would correspond to numpy/tests/test_dual.py . A lot of modules
don't need to be tested bec
On 1/11/07, Stefan van der Walt <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 11, 2007 at 03:18:19PM -0800, Keith Goodman wrote:
> > I see a lot of 'No test file found' warnings when running
> > numpy.test(). What does that mean?
>
> It means your verbosity is set too high. You'll find that N.test(0,0)
On Thu, Jan 11, 2007 at 03:18:19PM -0800, Keith Goodman wrote:
> I see a lot of 'No test file found' warnings when running
> numpy.test(). What does that mean?
It means your verbosity is set too high. You'll find that N.test(0,0)
complains much less (although, realistically, you'd probably want t
I see a lot of 'No test file found' warnings when running
numpy.test(). What does that mean?
>> M.__version__
'1.0.1'
>> M.test(10,10)
Warning: No test file found in
/usr/lib/python2.4/site-packages/numpy/core/tests for module
Found 13 tests for numpy.core.umath
Found 9 tests for numpy.lib.ar
