Hi
On Wed, Sep 02, 2009 at 02:49:28PM +1000, Minh Nguyen wrote:
This issue is now ticket #6861
http://trac.sagemath.org/sage_trac/ticket/6861
On Tue, Sep 08, 2009 at 09:11:40AM +0200, Jan Groenewald wrote:
This issue is unresolved for me: users running sage -t in a system-wide
install
Hi Jan,
On Thu, Sep 10, 2009 at 7:50 PM, Jan Groenewald j...@aims.ac.za wrote:
SNIP
In fact, I am not sure how sage -t is supposed top work. Where should the
testfile
be? Even root cannot run it:
See ticket #6908
http://trac.sagemath.org/sage_trac/ticket/6908
for some instructions on
Hi
On Thu, Sep 10, 2009 at 08:06:19PM +1000, Minh Nguyen wrote:
In fact, I am not sure how sage -t is supposed top work. Where should the
testfile
be? Even root cannot run it:
See ticket #6908
http://trac.sagemath.org/sage_trac/ticket/6908
for some instructions on how to doctest.
Hi Jan!
On Sep 10, 11:28 am, Jan Groenewald j...@aims.ac.za wrote:
[...]
According to that I see no way for a user to use a systemwide sage
installation to test their own modules (not intended for ever
bing included in sage, just modules they write and wish to test;
in fact part of a course
Hi
On Thu, Sep 10, 2009 at 03:52:08AM -0700, Simon King wrote:
Anyway, you can use the environment variable SAGE_TESTDIR. I just did
the following on sage.math:
$ mkdir tst
$ export SAGE_TESTDIR=`pwd`/tst/
$ sage -t test.py
where test.py is some Python file in the working directory.
Hi Jan!
On Sep 10, 12:14 pm, Jan Groenewald j...@aims.ac.za wrote:
Hi
On Thu, Sep 10, 2009 at 03:52:08AM -0700, Simon King wrote:
Anyway, you can use the environment variable SAGE_TESTDIR. I just did
the following on sage.math:
$ mkdir tst
$ export SAGE_TESTDIR=`pwd`/tst/
$
Hi
On Thu, Sep 10, 2009 at 04:52:48AM -0700, Simon King wrote:
$ mkdir tst
$ export SAGE_TESTDIR=`pwd`/tst/
$ sage -t test.py
where test.py is some Python file in the working directory. It
worked!
We did this. It works with a test file doing simple instructions, not
Hi Minh,
On Sep 10, 12:12 pm, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi Simon,
On Thu, Sep 10, 2009 at 8:52 PM, Simon King simon.k...@nuigalway.ie wrote:
SNIP
If this is part of your problem then I can elaborate on how I clumsily
solved that problem.
I would love to know about the
Hi Jan,
On Sep 10, 1:01 pm, Jan Groenewald j...@aims.ac.za wrote:
0 j...@muizenberg:~$vim test.py
0 j...@muizenberg:~$mkdir tst
0 j...@muizenberg:~$mv test.py tst/
0 j...@muizenberg:~$export SAGE_TESTDIR=`pwd`/tst/
0 j...@muizenberg:~$sage -t test.py
Sorry, when I said test.py is in the
Hi
On Thu, Sep 10, 2009 at 05:41:47AM -0700, Simon King wrote:
On Sep 10, 1:01 pm, Jan Groenewald j...@aims.ac.za wrote:
0 j...@muizenberg:~$vim test.py
0 j...@muizenberg:~$mkdir tst
0 j...@muizenberg:~$mv test.py tst/
0 j...@muizenberg:~$export SAGE_TESTDIR=`pwd`/tst/
0
Hi Jan!
On Sep 10, 1:45 pm, Jan Groenewald j...@aims.ac.za wrote:
[...]
0 j...@muizenberg:~$sage -t test.py
ERROR: File ./test.py is missing
exit code: 1
Strange. If test.py is in your current directory, why isn't it found?
0 j...@muizenberg:~$sage -t ~/test.py
sage -t /home/jan/test.py
On Sep 10, 12:14 pm, Jan Groenewald j...@aims.ac.za wrote:
I am now trying to learn clone and hg to apply the patch at
http://trac.sagemath.org/sage_trac/attachment/ticket/6861/trac_6861_n...
...
patch failed, unable to continue (try -v)
patch failed, rejects left in working dir
The
Hi
This issue is unresolved for me: users running sage -t in a system-wide
install owned by root.
On Wed, Sep 02, 2009 at 02:49:28PM +1000, Minh Nguyen wrote:
This issue is now ticket #6861
http://trac.sagemath.org/sage_trac/ticket/6861
# give write permissions to everyone, same as /tmp/
0
13 matches
Mail list logo
