Re: [sage-devel] Doc-testing ouptut with dots

2016-07-11 Thread Kwankyu Lee
> > But one's interface shouldn't be dictated by what the doctester can > and can't do. I agree. > Does anyone know if there's a reason the standard > doctest flags (like #doctest: -ELLIPSES) don't work properly in Sage's > tests? > I investigated this. The doctest options(flags) is imp

Re: [sage-devel] Doc-testing ouptut with dots

2016-07-11 Thread Erik Bray
On Mon, Jul 11, 2016 at 1:21 PM, Andrew wrote: > Thanks David and Erik for your replies. I could not disable the doct-tests > so I have changed my output to: > > sage: print(CartanType(['A', oo]).ascii_art()) > ..---O---O---O---O---O---O---O---.. > -3 -2 -1 0 1 2 3 > > > which I thin

Re: [sage-devel] Doc-testing ouptut with dots

2016-07-11 Thread Andrew
Thanks David and Erik for your replies. I could not disable the doct-tests so I have changed my output to: sage: print(CartanType(['A', oo]).ascii_art()) ..---O---O---O---O---O---O---O---.. -3 -2 -1 0 1 2 3 which I think is good enough. Andrew On Friday, 8 July 2016 10:34:31

Re: [sage-devel] Doc-testing ouptut with dots

2016-07-08 Thread Erik Bray
On Thu, Jul 7, 2016 at 1:13 PM, Andrew wrote: > Hi! > > How do you doc-test output that starts with ...? The particular output that > I want to test is: > > sage: print(CartanType(['A', oo]).ascii_art()) > ...---O---O---O---O---O---O---O---... > -3 -2 -1 0 1 2 3 > > but sage complai

Re: [sage-devel] Doc-testing ouptut with dots

2016-07-07 Thread David Roe
On Jul 7, 2016 07:13, "Andrew" wrote: > > Hi! > > How do you doc-test output that starts with ...? The particular output that I want to test is: > > sage: print(CartanType(['A', oo]).ascii_art()) > ...---O---O---O---O---O---O---O---... > -3 -2 -1 0 1 2 3 > You could do sage: print(

[sage-devel] Doc-testing ouptut with dots

2016-07-07 Thread Andrew
Hi! How do you doc-test output that starts with ...? The particular output that I want to test is: sage: print(CartanType(['A', oo]).ascii_art()) ...---O---O---O---O---O---O---O---... -3 -2 -1 0 1 2 3 but sage complains with: ValueError: line 6 of the docstring for sage.combi

Re: [sage-devel] doc testing

2013-08-01 Thread William Stein
On Thu, Aug 1, 2013 at 5:49 PM, davidp wrote: > I have a file called hyperplane_arrangement.py in my home directory, and > when I run > > sage -t hyperplane_arrangement.py > Here, probably the full sage library is imported first, e.g., "from sage.all import *". > from my home directory, all test

[sage-devel] doc testing

2013-08-01 Thread davidp
I have a file called hyperplane_arrangement.py in my home directory, and when I run sage -t hyperplane_arrangement.py from my home directory, all tests pass. The same file appears in the directory SAGEHOME/devel/sage-test/sage/geometry. If I cd into that directory and run sage -t hyperplane

[sage-devel] Doc testing regression

2009-06-20 Thread Simon King
Dear all, at http://groups.google.com/group/sage-support/browse_thread/thread/534306c87e7fac7a I was asking about the apparently changed behaviour of "sage -t". Georg suggested to move the discussion to sage-devel, so, here it is... On 20 Jun., 22:10, gsw wrote: > On 20 Jun., 08:15, Simon King