Python web framework Django 1.3 released
After "nearly a year in the making" the Django developers have released version 1.3 of the Python based web framework. While features such as class based views, support for Python's logging facilities, easier handling of static files and a testing framework which supports and bundles the unittest2 library have been incorporated in the new version, the focus of development in 1.3 has been to resolve the smaller, long-standing feature requests. Other new features include configurable delete cascades, context markers and comments for translatable strings, improves built in template tags and multiple named cache support.
Although the developers attempt to introduce new features in a backwards-compatible fashion, in 1.3 some features such as mod_python support and the DjangoTestRunner have been marked as deprecated, ready for phasing out in later releases. There are also some backwards-incompatible changes, mostly forced by security related issues, including CSRF validation for AJAX requests, the removal of the ability for FileField to delete files and a change to PasswordInputs rendering behaviour. The developers have also disabled the "profanity filter" used by the comments app. Described as "woefully naive and prone to the Scunthorpe problem"; the developers have emptied the word list and suggest that anyone needing to avoid profanities should investigate other options.
There is no change in this release to the Python compatibility of Django; it is still compatible with any version of Python 2.4 upwards, but 1.3 will be the final version to support 2.4. Minumum Python version for Django 1.4 will be 2.5 and the developers will be publishing their plans for completely deprecating Python 2.x and moving to Python 3.x soon.