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
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
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
> 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
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
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
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
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
Minh Nguyen wrote:
> Hi Jan,
>
> On Wed, Sep 2, 2009 at 2:31 PM, Jan Groenewald wrote:
>
>
>
>> Is there a ticket to fix this? .sage sounds good.
>
> This issue is now ticket #6861
>
> http://trac.sagemath.org/sage_trac/ticket/6861
>
I posted a one-line patch to
http://trac.sagemath.org/
Hi Jan,
On Wed, Sep 2, 2009 at 2:31 PM, Jan Groenewald wrote:
> Is there a ticket to fix this? .sage sounds good.
This issue is now ticket #6861
http://trac.sagemath.org/sage_trac/ticket/6861
--
Regards
Minh Van Nguyen
--~--~-~--~~~---~--~~
To post to this
Hi
On Tue, Sep 01, 2009 at 06:33:59PM -0700, William A. Stein wrote:
> Note that this should be considered a workaround. It should be
> considered a bug that users without write permissions to the Sage
> install directory can't test their scripts.
> It would be much better for Sage to use te
Hi
On Wed, Sep 02, 2009 at 11:24:25AM +1000, Minh Nguyen wrote:
> > Is there then any control on the space used?
If they did have write (unadvisable) they could fill the disk
space with logs.
Jan
--
.~.
/V\ Jan Groenewald
/( )\www.aims.ac.za
^^-^^
--~--~-~--~~
On Sep 1, 2009, at 6:24 PM, Minh Nguyen wrote:
>
> Hi Jan,
>
> On Tue, Sep 1, 2009 at 11:37 PM, Jan Groenewald wrote:
>
>
>
>> Is "sage -t" used for testing one's own code?
>
> Yes.
>
>
>> Should /usr/local/src/sage-4.1.1/tmp/tmp be world-writeable?
>
> No since from a security point of view yo
Hi Jan,
On Tue, Sep 1, 2009 at 11:37 PM, Jan Groenewald wrote:
> Is "sage -t" used for testing one's own code?
Yes.
> Should /usr/local/src/sage-4.1.1/tmp/tmp be world-writeable?
No since from a security point of view you don't want regular users to
write anything there. Think of that tmp
Hi All,
I have a system-wide sage install for all users.
The source lives in /usr/local/src and all of it is owned
by root.root. I chown it after install so that it does not
have another user's permissions. A user had this problem:
On Tue, Sep 01, 2009 at 02:41:54PM +0200, Dirk Laurie wrote:
>
On Mon, Jun 8, 2009 at 6:20 PM, davidp wrote:
>
> On the file test.py, consisting of
>
> """
> EXAMPLES::
>
> sage: gcd(4,6);
> sage: a = {1:'a',
> 2:'b'}
> """
>
> running sage -t produces two error messages (see below). Is it true
> that sage -t does not recog
16 matches
Mail list logo
