On Wed, Jun 2, 2010 at 5:46 PM, leif <[email protected]> wrote: > > > On 3 Jun., 02:30, William Stein <[email protected]> wrote: >> (sorry for the crossposting) >> >> On Wed, Jun 2, 2010 at 3:58 PM, leif <[email protected]> wrote: >> >> There is also an alpha1 of sage-4.4.3 here, and two tiny doctests failures >> >> >> >> >> http://sage.math.washington.edu/home/wstein/build/release/4.4.3/sage-... >> >> >> Failures on sage.math: >> >> >> sage -t -long "devel/sage/sage/graphs/generic_graph.py" >> >> > *Tiny* doctest failure?! This might break lots of documentation/texts >> > prepared with Sage (and I guess breaks the notebook output as well). >> > I've qualified this "critical", though I'd rather consider this a >> > blocker. (See ticket #9086.) >> >> Nobody proposed releasing Sage without fixing this. > > That's how I interpreted "tiny". ;-) > > >> >> sage -t -long "devel/sage/sage/sets/set.py" >> >> Total time for all tests: 8037.9 seconds >> >> >> This fails to build on OS X, due to some changes we made to get it to >> >> build on Cygwin. >> >> >> The alpha above makes almost no changes to the core Sage library. >> >> >> Of the "25 patches with positive review ready for inclusion" that you >> >> mentioned above, >> >> are they all changes to the core Sage library? Or do the patch spkg's, >> >> etc.? >> >> >> One possibility would be to test/stabilize the current 4.4.3.alpha* >> >> (i.e., fix the fallout from the cygwin >> >> related tickets), include those 25 patches (all to the sage library), >> >> and release 4.4.3 on Saturday. >> >> > Burcin said he won't be able to fix #9086 until next week... >> >> Burcin isn't the only person that knows how to work on Pynac. > > Probably.
I guess I can be more explicit. Getting Ginac to work with Python data types instead of CLN was my idea and I made it work. I wrote the first version of Pynac during an intense two week coding session in San Diego during August 2008. Burcin did a lot of development after that. Mike Hansen has also done a lot of work on Pynac. > I haven't looked deeper at it because it seemed to me *he* > certainly will (and quickly can) fix it as soon as he has time to do > so, i.e. next week. Also, at that time, I did not see an upcoming rc > or final. The more people who can fix or work on a given codebase the better. William -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
