On Wed, 24 Jan 2007 01:24:51 -0800, Iftikhar Burhanuddin <[EMAIL PROTECTED]>
wrote:
>
> I did a sage -upgrade on my sage-1.8 to get to sage-1.8.1 and I have the
> following question:
>
> Running sage -t foo.py creates the directory .doctest and the file
> ".doctest_foo.py". The reference manual section 4.3.1 claims such testing
> should create .doctest and the file ".doctest/foo.py". Should I edit
> prog.tex to mirror the actualities? Or is this behavior a bug?
I changed the doctest behavior recently so that now you can doctest
files anywhere (not necessary in SAGE), and type e.g.,
sage: from foo import *
sage: ...
in the doctest blocks and it will work, even if foo.py isn't part of the
SAGE library. It's much better now. Feel free to change the reference
manual to reflect this.
> Also what's the diff between foo.py and foo.sage? Is this documented
> anywhere? If not, I'll put it into prog.tex, once someone enlightens me,
> I'm guessing it's a question of with/without preparsing.
foo.py is the preparsed version of foo.sage. It says this right at
the beginning of foo.py (if you look at it):
# This file was *autogenerated* from the file foo.sage.
> BTW where's the SAGE preparser located at? There's nothing in prog.tex
> about preparsing and something needs to be said.
It's in devel/sage/misc/preparser*.py
William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
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/
-~----------~----~----~----~------~----~------~--~---
