That's a good idea William. I'm working on an automatic solution to
this problem.
Thanks for your encouragement!
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-
On Tue, Aug 11, 2009 at 9:43 PM, William Cauchois 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 form
On Tue, Aug 11, 2009 at 6:43 PM, William Cauchois 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 form
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 fo
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 wrote:
>
> I recently attached a patch to #1918 adding a displayhook to Sage that
> should make some output from the Sage interpreter much m
