(sorry for the crossposting) On Wed, Jun 2, 2010 at 3:58 PM, leif <not.rea...@online.de> 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. >> 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. >> If you like that, then make a clean sage-4.4.2, apply all 25 patches, >> test it, and I can just pull those >> changes in, and that will be 4.4.3. > > If module_list.py isn't affected by those patches... It depends on how module_list.py is effected. -- William -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
