[SciPy-dev] the scipy mission, include finite element solver

Dag Sverre Seljebotn dagss@student.matnat.uio...
Wed Apr 15 04:09:08 CDT 2009

Dag Sverre Seljebotn wrote:
> David Cournapeau wrote:
>> On Wed, Apr 15, 2009 at 8:37 AM, Andrew Straw <strawman@astraw.com> wrote:
>>> Well, fink ports the Debian package management to Mac OS X. Does
>>> something equivalent exist for Windows? The actual Debian file formats
>>> are pretty simple, so it seems like it should be do-able.
>> What makes debian such a well integrated system is not so much the
>> scripts - after all, rpm .spec files, debian files, port (BSd system)
>> files are not that different. What matters is how polish the actual
>> packages are. That's already difficult to do for one platform. That
> +1
> The reason Sage installs works is because Michael Abshoff works as 
> release manager. Making sure, e.g., that one software package isn't 
> upgraded until the rest of the packages can handle the upgrade.
> Ondrej, will SPD be keyed to Sage releases? Otherwise SPD will be 
> something that works at one point in time, but then requires fulltime 
> supervision to keep it working, and really not much better than 
> setuptools foir the reasons David mentions.

The major point I'm trying to make here is that if you have Sage version 
  x.y.z, that autoatically implies Python version a.b, NumPy version c.d 
and SciPy version e.f; all tested by someone else to fit together.

Unless the same will be the case for SPD, it just won't work as it must. 
And if it is not keyed 1:1 to Sage releases, there's going to be much 
work duplication.

The package system is not the problem; distribution maintainance is.

Dag Sverre

More information about the Scipy-dev mailing list