Andrew Godwin's latest in his Django migrations epic. After years of planning, he finally has functional code working with the Django core. He describes some of the new features and how legacy apps will be handled in this post.
A new Django forum sprung up recently. They describe it's reason for existence better than I could:
Welcome! Django Discussions is a place to converse about all things Django. It's aimed at filling the gap between Stackoverflow (where questions that solicit debate or opinion are generally avoided) and Google Groups (which is unsuited for lengthy discussion).
Those of you missing the old Convore discussions might find a happy home here.
Core developer, Luke Plant, has a bone to pick with Django being labeled as an "MVC" framework. He outlines why Django doesn't fit into the classic model and the confusion lumping them together causes.
Are you a Django lurker or know somebody that wants to get involved, but is scared of the command line? This is a great instructional post that walks somebody with no experience on the command line through the process of installing Django. The post is accompanied by two videos as well.
An opinionated post by Sentry developer David Cramer on his affinity for uWSGI as a Python web server over other options such as gunicorn. He outlines the setup he uses to help Sentry withstand the barrage of requests it receives daily.
On sites with lots of user generated content, getting a workable development environment in place can be a challenge. While database dumps are usually small enough to pass around, multiple gigs of files aren't. This post presents a solution that lets you default to local storage, but fallback to a different storage if files aren't found.
While Django's test runner takes care of cleaning up the database between runs, it doesn't do the same thing with files uploaded during the tests. This blog post from Mark Lavin introduces a Mixin that forces the test runner to clean up
after each run.
New & Updated Packages
A quick addition to
to allow it to pick up your Heroku environment variables from