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. > These kind of changes in OSS is one of the weaknesses, backward compatibility > is often being broken. I have plenty of commercial software that gets broken every time my commercial operating system gets updated. If anything, I'd argue that the advantage of OSS is that any of us can roll up our sleeves and fix it when this happens, as opposed to waiting on one or more companies to release a new black box.
