Django 1.3 Released

by Glyn Mooney

As you may have have discovered the eagerly awaited iteration of Django 1.3 has finally been released. The major focus of this release has been long standing feature requests, bug fixes and additions to current features. So without any further ado, lets run through them.

New Django 1.3 Features

  • Class based views
  • Framework support of the Python logging module
  • A new contribution for handling static media (images, javascript, css, etc.) now with netter support for CDN delivery out of the box
  • Support for the Python 2.7 unittest2
  • If your Python install is version 2.5 and above you’ll have access to the new transaction management functionality, similar to the .NET NHibernate
  • Configurable delete cascade functionality like Ruby on Rails Activerecord
  • Improvements to the current template tags. The load tag supports importing and loading from libraries, include allows the inclusion of extra context variables and the exclusion of the current context
  • A new TemplateResponse class to allow HTTP Responses to be withheld and changed later in the response process
  • An improved caching infrastructure
  • Support to grant permissions on inactive users. This will be useful if you require a user to access account information after authentication, or you just want to show them the account is awaiting activation
  • Django 1.3 ships with the GeoDjango test suite
  • MEDIA_URL and STATIC_URL settings must end with a slash! This is important if you intend to upgrade

To get the full list of changes (including the all important deprecation list) head over to the change list in the Django 1.3 documentation http://docs.djangoproject.com/en/dev/releases/1.3/