On Jun 3, 6:16 pm, Mats <[EMAIL PROTECTED]> wrote: Hi Mats,
> Hey it happens sometimes; at least you guys help users with a > quickfix. =) Thank you. ;) > One might prevent such future problems by adding this to unit tests > (if it doesn't exist already) and checking before release. We have extensive tests for Sage, i.e. one and a half hours of CPU time for the Sage library alone, but that one slipped by the DSage unit tests as well as the general doctests and we were just as surprised as you that it didn't get caught. That is why any new patch merged must be 100% doctested. Additionally we have been actively adding doctests to existing code and the goal is to have 100% of Sage functions doctested. Right now we are slightly over 52%. > Thanks, > Mats Cheers, Michael > On Jun 3, 10:16 am, "William Stein" <[EMAIL PROTECTED]> wrote: > > > On Tue, Jun 3, 2008 at 7:15 AM, William Stein <[EMAIL PROTECTED]> wrote: > > > On Tue, Jun 3, 2008 at 5:14 AM, Mats <[EMAIL PROTECTED]> wrote: > > > >> Unfortunately the example in the docs doesn't work (bug?), so I'm > > >> checking with the sage-devel group. > > >> Thank you however! > > > > You've encountered the "one big bug" in sage-3.0.2. > > > See > > >http://trac.sagemath.org/sage_trac/ticket/3311 > > > where we fixed it. > > > > I think you can fix the bug "by hand", by simplying copying > > > SAGE_ROOT/local/bin/dsage* to > > > SAGE_ROOT/local/lib/python/site-packages/sage/dsage/scripts > > > > I'm terribly sorry for this major bug getting into sage-3.0.2. > > > By the way, we'll release sage-3.0.3 within a few days, which > > will of course fix this problem. > > > William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
