First of all, use the "code" tags (shortcut as "#" in the composition panel) when you post code. Otherwise the whitespace don't show and it becomes very hard to follow any Python you post.
The Traceback thing is Python's way of delivering error messages. You will get those in CivIV Python also, so you might as well know this now.
Once you get a error message the interpreter will show a "traceback", from the original call in main and through any modules and functions you have called. That way you can actually follow the entire process and - hopefully - realize what the problem is.
So there is no Traceback command or statement in Python - the error message is the trace, back to where you initiated the code. Just do what the textbook says in order to produce the traceback in the example, and it should become apparent to you.
Don't worry about it if you don't fully understand this now, you can revisit it when you read up more on trouble shooting.
ps You managed to get Bruce to eat his Spam alright?
The Traceback thing is Python's way of delivering error messages. You will get those in CivIV Python also, so you might as well know this now.
Once you get a error message the interpreter will show a "traceback", from the original call in main and through any modules and functions you have called. That way you can actually follow the entire process and - hopefully - realize what the problem is.
So there is no Traceback command or statement in Python - the error message is the trace, back to where you initiated the code. Just do what the textbook says in order to produce the traceback in the example, and it should become apparent to you.
Don't worry about it if you don't fully understand this now, you can revisit it when you read up more on trouble shooting.
ps You managed to get Bruce to eat his Spam alright?