Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3 Brokers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cpu affinity on OS X at this time. 14 Chapter 1. Features Django Q Documentation, Release 1.3.6 1.3 Brokers The broker sits between your Django instances and your Django Q cluster instances; accepting Django’s Cache framework configured for monitoring • Compatible with Tynd Disque addon on Heroku 1.3. Brokers 15 Django Q Documentation, Release 1.3.6 • Still considered Alpha software • Supports bulk

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3 Brokers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . requires the optional psutil module. Psutil does not support cpu affinity on OS X at this time. 1.3 Brokers The broker sits between your Django instances and your Django Q cluster instances; accepting of a task by configuring the retry setting. Bulk task retrieval is supported via the bulk option. 1.3. Brokers 15 Django Q Documentation, Release 1.3.6 • Delivery receipts • Atomic • Needs Django’s

Django 1.2.x Getting 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 MultipleObjectsReturned while rendering 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 Extending the CMS 1. Extending the CMS: Examples 1.1. My First Plugin 1.2. My First App (apphook) 1.3. My First Menu 2. Custom Plugins 2.1. Why would you need to write a plugin? 2.2. Overview 2.3. The

Upgrading a django CMS installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 Introductory Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introductory Tutorial. 1.1.1 Requirements • Python 2.5 (or a higher release of 2.x). • Django 1.2.5 (or a 1.3.x release). • South 0.7.2 or higher • PIL 1.1.6 or higher • django-classy-tags 0.3.4.1 or higher • install python2.6 python-setuptools python-imaging sudo easy_install pip sudo pip install Django==1.3 django-cms south Additionally, you need the python driver for your selected database: sudo aptitude

Inherit Advanced 1. Internationalization 1.1. Multilingual URL Middleware 1.2. Language Chooser 1.3. page_language_url 1.4. CMS_HIDE_UNTRANSLATED 2. Sitemap Guide 2.1. Sitemap 2.2. Configuration 2 Extending the CMS: Examples index modules | next | 1.1. My First Plugin 1.2. My First App (apphook) 1.3. My First Menu 2. Custom Plugins 2.1. Why would you need to write a plugin? 2.2. Overview 2.3. The fields Contributing to 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 Indices and tables Index Module

issues) • django-sekizai 0.7 or higher • html5lib 0.90 or higher • django-i18nurls (if using django 1.3.X) • An installed and working instance of one of the databases listed in the Databases section. Note: WymEditor handling • Fix bugs in migrations • Fix bug in language fallback • Minor documentation fixes 1.3 2.4 release notes 1.3.1 What’s new in 2.4 Warning: Upgrading from previous versions 2.4 introduces Django 1.5 support, dropped support for Django 1.3 and Python 2.5 Django CMS 2.4 introduces Django 1.5 support. In django CMS 2.4 we dropped support for Django 1.3 and Python 2.5. Django 1.4 and Python 2.6

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 internals 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 How handle a wider array of situations. This is one of the reasons generic views were redesigned for the 1.3 release - previously, they were just view functions with a bewildering array of options; now, rather

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.3 The model layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static files • Advanced Tutorials: How to write reusable apps | Writing your first patch for Django 1.3 The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating handle a wider array of situations. This is one of the reasons generic views were redesigned for the 1.3 release - previously, they were just view functions with a bewildering array of options; now, rather