[sage-support] Re: sage -t has changed recently ?

2012-02-21 Thread John H Palmieri
On Tuesday, February 21, 2012 5:24:22 AM UTC-8, Laurent Claessens wrote: > > Hi all ! > > I want sage -t to test my docstrings. > [snip] Is it normal ? With older versions of sage the same docstring was working. > Are you sure it was working before? Is it possible that with earlier versions of

[sage-support] Re: sage -t has changed recently ?

2012-02-21 Thread Jason Grout
On 2/21/12 11:42 AM, William Stein wrote: On Tue, Feb 21, 2012 at 9:38 AM, Starx wrote: But what if I don't want to add "from ... import *" at the beginning of each docstring ? I had this issue recently. William informed me that the philosophy of doctests is that a user should be able to tak

Re: [sage-support] Re: sage -t has changed recently ?

2012-02-21 Thread William Stein
On Tue, Feb 21, 2012 at 9:38 AM, Starx wrote: >> But what if I don't want to add "from ... import *" at the beginning of each >> docstring ? > > I had this issue recently.  William informed me that the philosophy of > doctests is that a user should be able to take anything they see in a > doctest

Re: [sage-support] Re: sage -t has changed recently ?

2012-02-21 Thread Starx
> But what if I don't want to add "from ... import *" at the beginning of each > docstring ? I had this issue recently. William informed me that the philosophy of doctests is that a user should be able to take anything they see in a doctest and type it directly into sage with no additional comman

Re: [sage-support] Re: sage -t has changed recently ?

2012-02-21 Thread Laurent
On 21 Feb., 14:24, Laurent wrote: Is it normal ? With older versions of sage the same docstring was working. Really? I doubt it. Yes, really ;) Well, in fact I did not tested THAT example on Sage 4.7, but my usual programs had doctrings that were working on 4.7 and that are no more w

[sage-support] Re: sage -t has changed recently ?

2012-02-21 Thread Keshav Kini
Simon King writes: > Hi Laurent, > > On 21 Feb., 14:24, Laurent wrote: >> Is it normal ? With older versions of sage the same docstring was working. > > Really? I doubt it. Could be. https://groups.google.com/d/msg/sage-devel/KFSg46vgXuE/Krh9gzIz7EgJ But it must have been a very old version of

[sage-support] Re: sage -t has changed recently ?

2012-02-21 Thread Simon King
Hi Laurent, On 21 Feb., 14:24, Laurent wrote: > Is it normal ? With older versions of sage the same docstring was working. Really? I doubt it. Your doc test will work if and only if "my_function" is defined in sage.all if and only if "my_function" is available directly after starting an interac

[sage-support] Re: sage -t has changed recently ?

2012-02-21 Thread Keshav Kini
I don't know about whether this behavior has changed recently, but as far as I know, `sage -t` doesn't currently work on files that are not in the Sage library directory. This is not ideal and people were talking about trying to fix it recently: https://groups.google.com/d/msg/sage-devel/KFSg46vgX