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 <kntri...@gmail.com> 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 <filename>, I get mysterious errors.
>
> For instance, in sage/rings/, if I do  sage -t complex_interval.pyx, (I
> think this goes through for any .pyx file from my cursory looking into what
> flows on the screen when I do sage -t * in a directory...), I get that very
> large file, I am attaching.
>
> Questions:
>
> 1) Is this one one of the intended uses of the 't' flag: sage -t
> <filename>.pyx? You may assume that <filename>.pyx exists at pwd.
>
> 2) If the answer to the above is yes, how do I fix the problem I am facing?
>
> Notes about the Sage distro: Sage 5.7.beta4. I have other versions all built
> from source at the ~/Downloads/ along with this one.
>
> Hope someone would help. Thank you. ~KnS
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to