On Wednesday, September 21, 2011 9:47:37 AM UTC+8, John H Palmieri wrote:
>
>
>
> Another option: should we by default delete the preparsed file
> automatically after using it? That is, if you do "sage file.sage", then
> "file_preparsed.py" (or something like that) would be created, then fed into
> sage-python, and then deleted at the end. If you wanted to keep the file,
> you could run "sage -preparse file.sage" on its own.
>
This seems like a good idea :)
> Or I suppose we could store the preparsed files in ~/.sage/preparsed/, with
> filenames modified to reflect the full path of the original file (so you can
> have different files "script.sage" in several different directories, and the
> preparser will create different .py files for each one).
>
What if I want to load a file using load('./my_file.py')? Currently this
works if the preparsed file is in the same (relative) directory. But moving
it to ~/.sage/... will break it.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
