Chapter 9, Common Patterns for Forms (PDF) is a good representation of the writing style, code samples, and general feel of the book.
Click any of the following to read third-party reviews of this book.
Two Scoops of Django covers common best practices, including the following:
Tips and tricks for setting up your computer with Django and important tools the most optimal way.
We were part of the massive rewrite of Django's official class-based view documentation. In the book we cover the gray area where the docs end and specific use cases begin.
Django has a good security record. Help keep it that way by learning how to lock down and secure your projects.
Is your project running slow? We cover how to determine where bottlenecks exist and how to fix them.
Daniel gave the DjangoCon 2011 Advanced Django Form Usage talk and is updating it for PyCon 2013. Gain a deeper understanding of forms through his detailed examples.
Manage your settings/dependencies for different environments such that 100% of settings and 0% of secret keys are in version control.
We provide everything you need to know about concrete, abstract, and proxy models.
Extend abstract base User classes to store the data you need.
This book is loaded with code examples. We've gone the extra mile to put together great examples for you.
Here is a snapshot of the table of contents from Two Scoops of Django: Best Practices for Django 1.5.
After seeing other fellow developers struggle to get past the same sorts of basic hurdles in Django we had to overcome, we realized that much of the Django knowledge that we take for granted is not written down with examples anywhere.
We decided to take everything we know and write it down. Along the way, we learned even more from others and wrote those things down as well.
While this edition is frozen, feedback from hundreds of readers made its way into the forthcoming 1.6 edition.
If you’re struggling with finances and can’t afford it, let us know and we’d be happy to send you a free PDF of this 1.5 edition. Drop us a note at [email protected] and we’ll try to get it to you within 72 hours.
For more information, please read the FAQ.