On Dec 27, 9:18 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What *standard* Sage spkg packages are out of date right now
> (I'm skimminghttp://sagemath.org/components.html)?
>
> * cddlib: we ship 094b, but 094d is current.
#1619
> * clisp: we ship clisp-2.41, but 2.43 is current (I'm sure you can
> comment!)
> * cvxopt: we ship 0.9 but 0.9.1 is out. It has "efficient Python
> classes for dense and sparse matrices (real and complex), with Python
> indexing and slicing and overloaded operations for matrix arithmetic"
#1620
> -- looks cool!
> * gd: we ship 2.0.33 but 2.0.36 is current
#1621
> * gfan: we ship 0.2.2 but 0.3 is current
#1010
> * givaro: we ship 3.2.6 but 3.2.9 is current
#1035
> * gmp: we ship 4.2.1 but 4.2.2 is current
#542
> * gnutls: we ship 1.6.3 but 2.2.0 is current!
#1622
> * gsl: we ship 1.9 but 1.10 is current
#1623
> * jsmath: I don't even know what we ship (it's at most 3.4d), but
> current is 3.4f
#1624
> * iml: we ship 1.0.1, but 1.0.2 is current (I think 1.0.2 is
> upstreaming our changes
> in a way that breaks things for us...)
#748
> * ipython: we ship 0.8.1, but 0.8.2 is current
#1625
> * lcalc: we ship 20070107, but 20070902 is current.
#1626
> * libgcrypt: 1.4
#1627
> * Maxima: we ship 5.13, but 5.14 is current.
#1470
> * Moinmoin: we ship 1.5.7 but 1.5.8 is current
#1628
> * numpy: we ship 1.0.3 but 1.0.4 is current
#1629
> * opencdk: we ship 0.5.9 but 0.6.6 is current
#1630
> * pari: we ship 2.3.2 but 2.3.3 is current (I posted a new spkg tonight)
#1603
> * pexpect: we ship 2.0 but 2.3 is current (2.1 sucked (!); maybe 2.3 is
> good??)
#502 - that one is quite old :)
> * lippng: we ship 1.2.22, but 1.2.24 is current
tricky, no ticket yet.
> * quaddouble: we ship 2.2, but 2.3.1 is current
#1631
> * sqlite: we ship 3.5.3 but 3.5.4 is current
#1632
> * sympy: we ship 0.5.7 but 0.5.9 is current
#1633
> * zodb: we ship 3.7.0 but 3.7.2 is current
#1634
<SNIP>
I think that Robert's last point about not just upgrading for the fun
of upgrading valid. But as the matplotlib episode shows even a point
release might fix bugs that we haven't fixed yet like the scale issue.
There is certainly a cost/benefit ratio and we shouldn't go nuts, but
I assume that many people do not actually report bugs from Sage and
its components.
I did work on the Cygwin port of 2.9.1.1 for the last 36 hours and
since I fixed some platform specific bugs for the n-th time (n>5 in
some cases) I would really like everybody who maintains a spkg to push
our fixes upstream and also establish a working relation ship with the
developers of said spkg.
Timothy Clemans has volunteered offlist to manage the wiki pages with
maintenance info.
I will subscribe the the announce mailing lists of all of the projects
we include in case I am not already on the mailing list :). We should
actually create something like that because if you do not read sage-
devel or sage-support chances are you might miss some release. It is
more and more my impression that people are slow to upgrade if a
release works for them, but that observation is besides the point
here.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
