Chapter 10. When All Else Fails: Getting Outside Help
Sometimes we run into problems that do not seem to be caused by our own code. Though following the documentation to the best of our understanding, the results we are getting don't match what we expect. One of the benefits of building on open source code such as Django is that we can delve into its code and figure out exactly where things are going wrong. However, that may not be the best use of our time.
Most often a better first step in tracking down such problems is to consult community resources. Perhaps someone else has already encountered the problem we are facing and found a fix or workaround. If so, we can likely save a lot of time by taking advantage of their experience rather than finding our own solution to the problem.
This chapter describes the Django community resources and illustrates how to use them. Specifically, in this chapter we will:
Walk through the discovery of a bug that existed in the Django 1.1 release and caused...
