Hi Johnathan, I went ahead and re-updated my scipy and matplotlib as well, so a test output with numpy-1.7.0 pysparse-1.1.1 scipy-0.11.0 matplotlib-1.2.0 I got 6 errors http://pastebin.com/BHadSKBE
A number of them seem to be related to gmsh, but I also do get the two errors you mentioned. I can rebuild gmsh in case there was something amiss having updated numpy/scipy/matplotlib, but I'd be a bit surprised by that because gmsh doesn't depend on any of those. I'm also available to try other things you think may be helpful. Cheers, Ray On Wed, Mar 20, 2013 at 4:54 PM, Jonathan Guyer <[email protected]> wrote: > > On Feb 22, 2013, at 2:27 PM, Raymond Smith wrote: > > > So as far as I can tell, you were exactly right, and numpy-1.7.0 was > causing the issues. If there's anything else I can do that would help > clarify what's going on or help ease the transition to numpy-1.7.0, let me > know. > > Can you try again with the released version of NumPy 1.7.0? > > I see from your log at http://pastebin.com/grn7Maki that you were running > numpy version 1.7.0b2 when you got all those errors. I have not yet tested > on Ubuntu, but on my Mac OS X machine I get only two of those errors > ("IndexError: index 34417792 is out of bounds for axis 0 with size 2" and > "ImportError: cannot import name _formatInteger"), plus a third error that > seems unique to my machine (and which I also get with NumPy 1.6.1). > > The first two issues are filed as http://matforge.org/fipy/ticket/556 and > http://matforge.org/fipy/ticket/557. > _______________________________________________ > fipy mailing list > [email protected] > http://www.ctcms.nist.gov/fipy > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] >
_______________________________________________ fipy mailing list [email protected] http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
