Book Image

Django 1.1 Testing and Debugging

Book Image

Django 1.1 Testing and Debugging

Overview of this book

Bugs are a time consuming burden during software development. Django's built-in test framework and debugging support help lessen this burden. This book will teach you quick and efficient techniques for using Django and Python tools to eradicate bugs and ensure your Django application works correctly. This book will walk you step by step through development of a complete sample Django application. You will learn how best to test and debug models, views, URL configuration, templates, and template tags. This book will help you integrate with and make use of the rich external environment of test and debugging tools for Python and Django applications. The book starts with a basic overview of testing. It will highlight areas to look out for while testing. You will learn about different kinds of tests available, and the pros and cons of each, and also details of test extensions provided by Django that simplify the task of testing Django applications. You will see an illustration of how external tools that provide even more sophisticated testing features can be integrated into Django's framework. On the debugging front, the book illustrates how to interpret the extensive debugging information provided by Django's debug error pages, and how to utilize logging and other external tools to learn what code is doing.
Table of Contents (17 chapters)
Django 1.1 Testing and Debugging
Credits
About the Author
About the Reviewer
Preface
Index

Developing an Apache/mod_wsgi configuration


Ordinarily, the move to production will involve running the code on a machine other than the ones it has been developed on. The production server might be dedicated hardware or resources obtained from a hosting provider. In either case, it is typically entirely separate from the machines used by developers when writing the code. The production server needs to have any of the pre-requisite packages installed (Django and matplotlib, for example, for our sample project). In addition a copy of the application project code, generally extracted from a version control system, needs to be placed on the production server.

For the sake of simplicity in this chapter, though, we are going to configure a production web server on the same machine where we have been developing the code. This will allow us to skip over some of the complexity involved in a real move to production while still experiencing many of the issues that may arise during production deployment...