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 releases Django 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 Tags both with and without time zone support. Fixtures generated with USE_TZ = False, or before Django 1.4, use the “naive” format. If your project contains such fixtures, after you enable time zone support

layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.4 The view layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Legacy databases | Providing initial data | Optimize database access | PostgreSQL specific features 1.4 The view layer Django has the concept of “views” to encapsulate the logic responsible for processing both with and without time zone support. Fixtures generated with USE_TZ = False, or before Django 1.4, use the “naive” format. If your project contains such fixtures, after you enable time zone support

Started 1. Introductory Tutorial 1.1. Getting help 1.2. Configuration and setup 1.3. Creating templates 1.4. Creating your first CMS Page! 2. Using South with django CMS 2.1. Installation 2.2. Basic usage 2 Advanced 1. Internationalization 1.1. Multilingual URLs 1.2. Language Cookie 1.3. Language Chooser 1.4. page_language_url 1.5. hide_unstranslated 1.6. Automated slug generation unicode characters 2. Sitemap django CMS 1. Contributing to django CMS 1.1. Community 1.2. In a nutshell 1.3. Contributing Code 1.4. Contributing Documentation 1.5. Translations 2. Running and writing tests 2.1. Running tests 2.2.

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 releases Django 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 Tags both with and without time zone support. Fixtures generated with USE_TZ = False, or before Django 1.4, use the “naive” format. If your project contains such fixtures, after you enable time zone support

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 releases Django 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 Tags both with and without time zone support. Fixtures generated with USE_TZ = False, or before Django 1.4, use the “naive” format. If your project contains such fixtures, after you enable time zone support

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.4 The model layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . admin site • Advanced Tutorials: How to write reusable apps | Writing your first patch for Django 1.4 The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating both with and without time zone support. Fixtures generated with USE_TZ = False, or before Django 1.4, use the “naive” format. If your project contains such fixtures, after you enable time zone support

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.4 The model layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . admin site • Advanced Tutorials: How to write reusable apps | Writing your first patch for Django 1.4 The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating both with and without time zone support. Fixtures generated with USE_TZ = False, or before Django 1.4, use the “naive” format. If your project contains such fixtures, after you enable time zone support

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 releases Django 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 Tags both with and without time zone support. Fixtures generated with USE_TZ = False, or before Django 1.4, use the “naive” format. If your project contains such fixtures, after you enable time zone support

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 releases Django 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 Tags both with and without time zone support. Fixtures generated with USE_TZ = False, or before Django 1.4, use the “naive” format. If your project contains such fixtures, after you enable time zone support

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 releases Django 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 Tags both with and without time zone support. Fixtures generated with USE_TZ = False, or before Django 1.4, use the “naive” format. If your project contains such fixtures, after you enable time zone support