Python 2.5.2 (r252:60911, Feb 22 2008, 07:57:53) 
[GCC 4.0.1 (Apple Computer, Inc. build 5363)]
Type "help", "copyright", "credits" or "license" for more information.
>>> # What we did in the shell was just warming us up 
>>> # for running the programs
>>> #
>>> # We went through the *py files, tracing each of them, 
>>> # and watching what was happening in the "stack data"
>>> # window.  
>>> # Generally speaking, to trace a program, type "step into" 
>>> # once.  If you want to see all the details (such as watching
>>> # the funtion calls), then continue using "step into".  We did 
>>> # this to see the functions calling each other.  
>>> # If a statement involves something defined in another file -
>>> # for example, any statement that includes "media." in it, then
>>> # use "step over".  Otherwise, you will start seeing what
>>> # is executed in the separate module, even though you don't care
>>> # about those details.  
>>> #
>>> # If you ever "stepped in" when you didn't want to, just use 
>>> # "Step Out" repeatedly until you get back where you want to be.