Where is walk.py located after I attach walk.sage?

edit

Nice - that is useful! But of course there is a walk.py ;-)

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."?

Also, I wonder if sometimes it *does* create walk.py in the proper directory. At least, I have some .py files I didn't create that are in the same directory as the .sage files I use for my research. But I always have to call them with the full /path/to/file.sage, so maybe that makes a difference as opposed to rtwalker's use case...

@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.

@John Palmieri after repeating my procedure I still could not find walk.py in the directory that you suggested (all there was was an empty 'interface' directory. Regardless, with your sage --preparse suggestion I can force sage to make me a walk.py file. Thanks