Comment by rtrwalker 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.

If my ultimate goal is to write some sort of package, is there any point to me writing *.sage files in the first place or should I start out writing *.py scripts and use "from sage.all import *" and prepend all the sage-functions I use with "sage.all."?