chose common simple errorsso hopefully you would have been able to figure out the meaning of the error message that is lot to expect in general we are only gradually adding explanations of bits of python syntax you can easily make an error that the python interpreter guesses as being based on more advanced featureso the error message makes no sense to you even if you do not understand the error messageyou should get the information about where the error occurred hopefully concentrated look there will lead to you seeing the error and being able to correct it if you did not understand the original error messagethen there is further useful step after you do figure it out (with or without outside help)go back and consider the error message again after seeing what was actually wrongthe error message may make sense nowand that knowledge may be useful to speed up your understanding and your fix the next time you see that error message particularly as beginneryou can still hit brick wall some of the timeeven with partner you are also in course with an instructorthat is major reason am here ask for help if considering the information provided by idleplus little thoughtare not enoughnested calls in traceback in the previous example programthe execution error occured outside of any function call there are further useful features in an error tracebackwhen there are errors inside function calls we illustrateshowing the outputwith error tracebackfor silly example programshowtraceback py'''program with intended error to demonstrate traceback from nested call''def invminus ( )return /( - def main()print('this program is intended to cause an execution error 'print('ok call to invminus ( next:'print(invminus ( )print('bad call invminus ( next:'print(invminus ( )print("won' get to here!"main(note that the first call to invminus with parameter is fine /( - in the execution of the call invminus ( )we get an error traceback message the image below comes after the traceback is displayedand then just as the user uses the mouse to select the line where the error wasnote that after the title line in the traceback there are three indented lines starting with "file"not just one line as in the earlier program the bottom file line shows the line where the error occurredand we could jump to the sourcecontinuing from the step in the previous imagethe error takes place in functionand function can be called in many places with different parameters the further up lines in the traceback show the chain of function calls to reach that occurrence of the error the program calls main in the bottom line of the program (line first file line reference)and then main calls invminus twice we can tell which call caused the errorsince the traceback shows the call to invminus at line if you had any question of the context for any of the nested calls leading to the erroryou could also select previous file line with the mouseand jump to the calling line in the source using error messages