On 4/23/07, Bill Hart <[EMAIL PROTECTED]> wrote:
> I re-ran the tests and the same error recurred (but with a different
> numbered temp directory of course). I checked in the sage temp
> directory and there seemed to be two numbered temp directories in
> there, one of which did not change, the other of which seemed to
> change with the doctest being run. Neither of them had the same number
> as the one it complained about.

OK, thanks.  Those files are created by SAGE normally, and cleaned
up when SAGE quits.  Probably I just need to redirect the output of a
rm command to /dev/null, but which output... I'll figure it out.

> Can someone explain the doctests to me. What do they actually test? In

They test every single example listed in every single python file in the
docstrings. As of now that is 23825 lines of input.

> particular, where are the actual doctests? I can't find any of the
> files called doctest.py that it is talking about, in any of the

They are hidden, i.e., begin with a dot.  Those files are created
from the corresponding python files.

> directories. I can certainly find the .py files that it is testing,
> but not the driver files for the tests.
>
> Also, at the end of the make process, I tried to type:
>
> install_scripts ( '/scratch' )
>
> using the syntax it recommended. It replied:

You have to type it in SAGE not on the bash command line.  I'll clarify
this in the message.

> Badly placed ()'s.
>
> I can't use the /usr/local/bin directory or whatever it recommends,
> because I do not have write permissions to that.
>
> Bill.
>
>
> >
>


-- 
William Stein
Associate Professor of Mathematics
University of Washington
http://www.williamstein.org

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to