debugging your application using pydbgr high-end idesuch as komodo idecomes with complete debugger even komodo edit comes with simple debugger howeverif you're using something smallerless expensiveand less capable than high-end ideyou might not have debugger at all debugger helps you locate errors in your application and fix them the better your debuggerthe less effort required to locate and fix the error when your editor doesn' include debuggeryou need an external debugger such as pydbgr ( reasonably good debugger includes number of standard featuressuch as code colorization (the use of color to indicate things like keywordshoweverit also includes number of nonstandard features that set it apart here are some of the standard and nonstandard features that make pydbgr good choice when your editor doesn' come with debuggersmart evalthe eval command helps you see what will happen when you execute line of codebefore you actually execute it in the application it helps you perform "what ifanalysis to see what is going wrong with the application out-of-process debuggingnormally you have to debug applications that reside on the same machine in factthe debugger is part of the application' processwhich means that the debugger can actually interfere with the debugging process using out-of-process debugging means that the debugger doesn' affect the application and you don' even have to run the application on the same machine as the debugger thorough byte-code inspectionviewing how the code you write is turned into byte code (the code that the python interpreter actually understandscan sometimes help you solve tough problems event filtering and tracingas your application runs in the debuggerit generates events that help the debugger understand what is going on for examplemoving to the next line of code generates an eventreturning from function call generates another eventand so on this feature makes it possible to control just how the debugger traces through an application and which events it reacts to