On Tue, Aug 11, 2009 at 6:43 PM, William Cauchois<[email protected]> wrote: > > I can't believe I forgot to run -testall! The displayhook was using > the wrong output stream in doctesting mode. I've managed to fix this > issue in my branch. However, I realize now that since the displayhook > changes the output format for some objects, any doctests which rely > upon the old output format will have to be modified. This appears to > be a significant number of doctests. In that case, maybe the > displayhook isn't worth it?
Or maybe this is an even stronger reason that it *is* worth it. Can you post a number of examples showing before/after, then see what people think? There are ways to automate fixing all doctests in a file, by the way... sage -fixdoctests or something like that... > On Tue, Aug 11, 2009 at 8:19 PM, David Joyner<[email protected]> wrote: >> >> There are a huge number of errors in sage -testall when applied to >> 4.1.1.rc2 on an intel macbook 10.4.11. >> >> >> On Tue, Aug 11, 2009 at 7:46 PM, William Cauchois<[email protected]> wrote: >>> >>> I recently attached a patch to #1918 adding a displayhook to Sage that >>> should make some output from the Sage interpreter much more readable. >>> Can anyone take a look at it at >>> <http://trac.sagemath.org/sage_trac/ticket/1918>? >>> >>> Thanks, >>> Bill Cauchois >>> >>> > >>> >> >> > >> > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ 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 URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
