Quantcast
Channel: ASKSAGE: Sage Q&A Forum - RSS feed
Viewing all articles
Browse latest Browse all 9

Comment by kcrisman for (Edit: I originally thought that there wasn't a file walk.py, but I think that's wrong.)Look in $HOME/.sage/temp/DIR0/DIR1/ where $HOME is your home directory, DIR0 has a name like $HOSTNAME and DIR1 is a number, the process id of the Sage process. This directory is deleted when you quit Sage.If you want to produce a more permanent file walk.py, then from your shell prompt, run sage --preparse walk.sage. This will produce walk.py in the current directory.

$
0
0
@rtwalker: I think that to start off, the advantage of the .sage files is that you get a quick start and can see what happens. Then when you make .py files out of them, you can later (usually by trial and error) figure out what you actually *need* to important, rather than doing the nasty import * trick. But everyone has a different preferred work flow, it's up to what makes you comfortable and productive.

Viewing all articles
Browse latest Browse all 9

Trending Articles