2010/10/19 Jonathan Guyer <[email protected]> > > > On Oct 19, 2010, at 2:47 PM, Jonathan Guyer wrote: > > > On Oct 19, 2010, at 11:35 AM, Benny Malengier wrote: > > > >> I noted the API for pysparse is greatly changed in development, so trunk > versions of pysparse will not work with current fipy. > >> It seems it will be possible to support the old and new version of > pysparse, with some development effort. I hope fipy chooses for that path. > > > > We're aware of the issue. We're waiting for pysparse to settle down > before we try and do anything with it. Whether we support both old and new > APIs will depend on how much a mess it makes of our own code and how much > trouble it is to build either old or new versions of pysparse. > > I take that back. I spoke with Wheeler and he's been making sure that > pysparse continues to support its old interface. Are you aware of things > that break? >
I don't track pysparse trunk anymore, so the issues might have been fixed in the meantime. Last I tried, there where problems with packages no longer existing (movement of directories), methods that where uncapitalised, that became capitalized, ... . If they follow that track, I'd go for a 2.0 release then instead of 1.2, which gives the impression the project is working on minor changes/improvements. Anyway, if the old interface remains for the moment, then that is great news. Benny
