On Wednesday, September 21, 2011 11:26:39 AM UTC-7, Felix Salfelder wrote: > > On Wed, Sep 21, 2011 at 09:11:57AM -0700, Tom Boothby wrote: > > I capitulate on the hidden file idea, in favor of putting 'em in > > ~/.sage/ though one might note that we're exchanging one hidden file > > for another ;) > > i agree. prefixing a dot is not quite a solution as i thought yesterday. > > putting them in ~/.sage would require some pathname mangling or hashing, > that wouln't make it easier to list/find them than a prefixed filename > (be it with a dot or not). > > if I got it right, caching the preparser output is for debugging or for > performance (correct me if im wrong). if it is for debugging, it would > be perfectly safe to hide it from the user, if it is for performance, it > would make more sense to put it into /tmp or /dev/shm. > 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.)
-- John -- 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