Re: [sage-devel] sage -t Help

2013-02-16 Thread Jeroen Demeyer
On 2013-02-16 14:36, Kannappan Sampath wrote: > So, could you please tell me how would I run this version of sage? It depends on what you want to do. If you *always* want that version of Sage, you could either: - change the file `which sage` to point to the directory you want (for example, by makin

Re: [sage-devel] sage -t Help

2013-02-16 Thread Kannappan Sampath
Dear Jeroen and John, Thank you for the replies. OK, thanks for the questions. One of them nails it On Sat, Feb 16, 2013 at 4:53 PM, Jeroen Demeyer wrote: > On 2013-02-16 05:30, Kannappan Sampath wrote: > > Hello everyone, > > > > I would be very glad if someone can please help me with this prob

Re: [sage-devel] sage -t Help

2013-02-16 Thread Jeroen Demeyer
On 2013-02-16 11:55, John Cremona wrote: > I think it works if you cd to SAGE_ROOT and do the sage -t from there > (with the full relative path to the file of course). That shouldn't be the problem, doctests are supposed to work from any directory: jdemeyer@sage:/release/merger/sage-5.8.beta0/deve

Re: [sage-devel] sage -t Help

2013-02-16 Thread Jeroen Demeyer
On 2013-02-16 05:30, Kannappan Sampath wrote: > Hello everyone, > > I would be very glad if someone can please help me with this problem. I > had wanted to review some doctest-adding patches. So, as a preliminary, > if I did sage -t , I get mysterious errors. I think we need more information ab

Re: [sage-devel] sage -t Help

2013-02-16 Thread John Cremona
I think it works if you cd to SAGE_ROOT and do the sage -t from there (with the full relative path to the file of course). John On 16 February 2013 04:30, Kannappan Sampath wrote: > Hello everyone, > > I would be very glad if someone can please help me with this problem. I had > wanted to review