From: Tim H. <tim...@ie...> - 2006-10-12 18:05:20
|
Is any one else seeing the multiarray tests all get skipped because of an import error when compiling under python 2.5. Everything else seems to work and all the tests go fine under 2.4. -tim |
From: Gerard V. <ger...@gr...> - 2006-10-12 18:13:51
|
On Thu, 12 Oct 2006 11:04:55 -0700 Tim Hochberg <tim...@ie...> wrote: > > Is any one else seeing the multiarray tests all get skipped because of > an import error when compiling under python 2.5. Everything else seems > to work and all the tests go fine under 2.4. Everything looks fine here: >>> sys.version '2.5 (r25:51908, Oct 8 2006, 07:23:15) \n[GCC 4.1.1 (Gentoo 4.1.1)]' >>> np.version.version '1.0.dev3317' >>> np.test() Found 13 tests for numpy.core.umath Found 9 tests for numpy.lib.arraysetops Found 36 tests for numpy.core.ma Found 3 tests for numpy.fft.helper Found 4 tests for numpy.ctypeslib Found 2 tests for numpy.lib.polynomial Found 8 tests for numpy.core.records Found 26 tests for numpy.core.numeric Found 5 tests for numpy.distutils.misc_util Found 3 tests for numpy.lib.getlimits Found 31 tests for numpy.core.numerictypes Found 4 tests for numpy.core.scalarmath Found 1 tests for numpy.lib.ufunclike Found 12 tests for numpy.lib.twodim_base Found 47 tests for numpy.lib.shape_base Found 4 tests for numpy.lib.index_tricks Found 32 tests for numpy.linalg.linalg Found 42 tests for numpy.lib.type_check Found 176 tests for numpy.core.multiarray Found 10 tests for numpy.core.defmatrix Found 41 tests for numpy.lib.function_base Found 0 tests for __main__ ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. ---------------------------------------------------------------------- Ran 509 tests in 0.265s OK <unittest.TextTestRunner object at 0x2aaaaed6a650> >>> Gerard |
From: Tim H. <tim...@ie...> - 2006-10-12 18:22:20
|
Gerard Vermeulen wrote: > On Thu, 12 Oct 2006 11:04:55 -0700 > Tim Hochberg <tim...@ie...> wrote: > > >> Is any one else seeing the multiarray tests all get skipped because of >> an import error when compiling under python 2.5. Everything else seems >> to work and all the tests go fine under 2.4. >> > > Everything looks fine here: > Thanks. I suppose that means it's either Windows specific or I gummed up my build tree somehow. I'll make a clean checkout and see if it goes away. -tim |
From: Tim H. <tim...@ie...> - 2006-10-12 18:35:49
|
Tim Hochberg wrote: > Gerard Vermeulen wrote: > >> On Thu, 12 Oct 2006 11:04:55 -0700 >> Tim Hochberg <tim...@ie...> wrote: >> >> >> >>> Is any one else seeing the multiarray tests all get skipped because of >>> an import error when compiling under python 2.5. Everything else seems >>> to work and all the tests go fine under 2.4. >>> >>> >> Everything looks fine here: >> >> > > Thanks. > > I suppose that means it's either Windows specific or I gummed up my > build tree somehow. I'll make a clean checkout and see if it goes away. > > Still there with a clean checkout. Blech! I hate weird import problems. I'll try to look into it, but if anyone has any good ideas, let me know -tim |
From: Travis O. <oli...@ee...> - 2006-10-12 19:27:35
|
Tim Hochberg wrote: >> >> >> >Still there with a clean checkout. Blech! I hate weird import problems. >I'll try to look into it, but if anyone has any good ideas, let me know > > Show us the errors, I may be able to help. It's possible some recent changes messed things up. -Travis |
From: Tim H. <tim...@ie...> - 2006-10-12 19:32:41
|
Travis Oliphant wrote: > Tim Hochberg wrote: > > >>> >>> >>> >>> >> Still there with a clean checkout. Blech! I hate weird import problems. >> I'll try to look into it, but if anyone has any good ideas, let me know >> >> >> > Show us the errors, I may be able to help. It's possible some recent > changes messed things up. > I just checked in a fix. I think it was some case problem in the paths that got set in set_local_path(). In any event, applying normpath to the merged path fixed the problem and I didn't feel like pursuing it further. -tim |