distributions of Django For distributors Glossary Release notes Final releases 1.8 release 1.7 release 1.6 release 1.5 release 1.4 release 1.3 release 1.2 release 1.1 release 1.0 release Pre-1.0 releases Security versions Long-term support (LTS) releases Release process Django Deprecation Timeline 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Other branches an intermediary model, you must use symmetrical=False (see the model field reference). In Django 1.6 and earlier, intermediate models containing more than one foreign key to any of the models involved

template layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.6 Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Built-in tags and filters | Humanization • For programmers: Template API | Custom tags and filters 1.6 Forms Django provides a rich framework to facilitate the creation of forms and the manipulation of an intermediary model, you must use symmetrical=False (see the model field reference). In Django 1.6 and earlier, intermediate models containing more than one foreign key to any of the models involved

Final releases 2.1 release 2.0 release 1.11 release 1.10 release 1.9 release 1.8 release 1.7 release 1.6 release 1.5 release 1.4 release 1.3 release 1.2 release 1.1 release 1.0 release Pre-1.0 releases Security policy Supported versions Release process Django Deprecation Timeline 3.0 2.1 2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Other branches not be synchronized. select_on_save Options.select_on_save Determines if Django will use the pre-1.6 django.db.models.Model.save() algorithm. The old algorithm uses SELECT to determine if there is an

2.2 release 2.1 release 2.0 release 1.11 release 1.10 release 1.9 release 1.8 release 1.7 release 1.6 release 1.5 release 1.4 release 1.3 release 1.2 release 1.1 release 1.0 release Pre-1.0 releases Security Supported versions Release process Django Deprecation Timeline 3.1 3.0 2.1 2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Stable branches not be synchronized. select_on_save Options.select_on_save Determines if Django will use the pre-1.6 django.db.models.Model.save() algorithm. The old algorithm uses SELECT to determine if there is an

Tutorials. Requirements • Python 2.6, 2.7, 3.3 or 3.4. • Django 1.6.x, 1.7.x, 1.8.x • South 1.0.1 or higher (Only required up to Django 1.6) • django-classy-tags 0.6.2 or higher • django-treebeard 3.0 Pillow (fork of PIL) for image manipulation Revision management • django-reversion 1.8.X (with Django 1.6.X and Django 1.7.X) to support versions of your content (If using a different Django version it is 'database.sqlite'), } } django CMS, as well as its plugins, supports both Django 1.7 and Django 1.6 migrations. Since version 3.1, migrations are stored in modules compatible with Django 1.7 and South

Glossary Release notes Final releases 1.11 release 1.10 release 1.9 release 1.8 release 1.7 release 1.6 release 1.5 release 1.4 release 1.3 release 1.2 release 1.1 release 1.0 release Pre-1.0 releases Security Deprecation policy Supported versions Release process Django Deprecation Timeline 2.1 2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Other branches the last version to support Python 3.3. What Python version should I use with Django? As of Django 1.6, Python 3 support is considered stable and you can safely use it in production. See also Porting to

distributors Glossary Release notes Final releases 1.10 release 1.9 release 1.8 release 1.7 release 1.6 release 1.5 release 1.4 release 1.3 release 1.2 release 1.1 release 1.0 release Pre-1.0 releases Security Deprecation policy Supported versions Release process Django Deprecation Timeline 2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Other branches the last version to support Python 3.3. What Python version should I use with Django? As of Django 1.6, Python 3 support is considered stable and you can safely use it in production. See also Porting to

layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.6 The template layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Advanced: Generating CSV | Generating PDF • Middleware: Overview | Built-in middleware classes 1.6 The template layer The template layer provides a designer-friendly syntax for rendering the information not be synchronized. select_on_save Options.select_on_save Determines if Django will use the pre-1.6 django.db.models.Model.save() algorithm. The old al- gorithm uses SELECT to determine if there is an

Release notes Final releases 2.0 release 1.11 release 1.10 release 1.9 release 1.8 release 1.7 release 1.6 release 1.5 release 1.4 release 1.3 release 1.2 release 1.1 release 1.0 release Pre-1.0 releases Security policy Supported versions Release process Django Deprecation Timeline 3.0 2.1 2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Other branches not be synchronized. select_on_save Options.select_on_save Determines if Django will use the pre-1.6 django.db.models.Model.save() algorithm. The old algorithm uses SELECT to determine if there is an

layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.6 The template layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Advanced: Generating CSV | Generating PDF • Middleware: Overview | Built-in middleware classes 1.6 The template layer The template layer provides a designer-friendly syntax for rendering the information version to support Python 3.3. 5.2.4 What Python version should I use with Django? As of Django 1.6, Python 3 support is considered stable and you can safely use it in production. See also Porting to