From: bryce h. <bhe...@en...> - 2006-06-15 17:41:41
|
We've had the same problem many times. There were a few causes: * Our clean scripts don't delete c++ files, so generated code was often not re-generated when we switched to numpy * Files to generate code had numeric arrays hardcoded * we were using numerix, and the env var was not set for part of the build How I generally detect the problem is by deleting the numeric/numarray package directories, then running python with the verbose flag. Bryce Fernando Perez wrote: > On 6/15/06, Eric Emsellem <ems...@ob...> wrote: > >> Hi, >> >> I have written a number of small modules where I now systematically use >> numpy. >> >> I have in principle used the latest versions of the different >> array/Science modules (scipy, numpy, ..) but still at some point during >> a selection, it crashes on numpy because it seems that the array >> correspond to "numarray" arrays. >> > > [...] > > >> QUESTION 1: Any hint on where numarray could still be appearing? >> > > Not a final answer, but I've had the same thing happen to me recently > (I'm making the transition right now) with extension modules which > were built against Numeric (in my case). They return old Numeric > arrays (I had 23.7, without the array interface) and numpy is not > happy. > > Rebuilding all my extensions against numpy fixed the problem. > > Cheers, > > f > > > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > > |