Summary

We've now come to the end of discussion of what to do when none of the other debugging techniques covered previously have succeeded in solving some problem. In this chapter, we:

• Encountered a bug that existed in Django 1.1 and caused some of the survey application code to not behave as desired

• Walked through the verification process of tracking down the problem to Django instead of the survey code

• Saw how searching in the Django code tracker revealed the problem was a bug that had been fixed in Django 1.1.1, which provided an easy solution to the problem

• Discussed options for how to proceed when problems are tracked down to bugs with fixes that are either not yet available or not available in official releases

• Described the various community resources that exist for asking questions about behavior that seems puzzling, but doesn't seem to have been reported as a bug

• Discussed tips for writing questions so that they get the desired helpful responses

• Described the process of opening a new...