On 2011-09-22 11:07, Volker Braun wrote:
> On Wednesday, September 21, 2011 7:53:16 PM UTC+1, John H Palmieri wrote:
>
> Another idea would be to not cache it at all: don't save any file,
> but save the preparsed file as a string and feed that in to
> sage-python. ("sage -preparse" would still wrute to a file.)
>
>
> I think that would be the best option. As far as I understand it, the
> preparser is just a glorified sed script so speed isn't an issue.
>
> Also, the lack of an autogenerated .py file floating around in the
> current directory makes things less mysterious to new users, if anything.
If this is feasible, then not creating any file is the best option: no
needless file clutter.
--
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
