org/3/library/asyncio.html#module-asyncio] module and shares the same event loop (by default since Tornado 5.0). In general, libraries designed for use with asyncio [https://docs.python.org/3/library/asyncio.html#module-asyncio] Tornado is available under the Apache License, Version 2.0 [http://www.apache.org/licenses/LICENSE-2.0.html]. This web site and all documentation is licensed under Creative Commons 3.0 [https://creativecommons of a thread. They also make concurrency easier [https://glyph.twistedmatrix.com/2014/02/unyielding.html] to reason about by reducing the number of places where a context switch can happen. Example: async

doing all of the following steps in a virtual environment [https://docs.python.org/3/library/venv.html]. You ought to know how to create, activate and dispose of virtual environments. If you don’t, you LICENSE README.md db.sqlite3 myproject/ static/ templates/ base.html __init__.py asgi.py settings.py urls.py wsgi.py manage project’s default template. In the root of the project, create a templates directory, and in that, home.html, a minimal django CMS template: This is worth explaining in a little detail: {% load cms_tags sekizai_tags

compatibility issues) django-sekizai [https://github.com/ojii/django-sekizai] 0.7 or higher html5lib [http://code.google.com/p/html5lib/] 0.90 or higher django-i18nurls [https://github.com/brocaar/django-i18nurls] installing the django CMS using pip, Django, django-mptt django-classy- tags, django-sekizai, south and html5lib will be installed automatically. Recommended These packages are not required, but they provide org], but we recommend using a requirements.txt [http://www.pip- installer.org/en/latest/cookbook.html#requirements-files] file. The following is an example requirements.txt file that can be used with

compatibility table for particular python version here [https://docs.django- cms.org/en/latest/index.html#software-version-requirements-and-release-notes] 1.2. Your working environment We’re going to assume default, the installer runs in Batch mode [https://djangocms- installer.readthedocs.io/en/latest/usage.html#batch-mode-default], and sets up your new project with some default values. Later, you may wish to case you need to run it in Wizard mode [https://djangocms-installer.readthedocs.io/en/latest/usage.html#wizard-mode]. The default in Batch mode is to set up an English-only project, which will be sufficient

default, the installer runs in Batch mode [https://djangocms- installer.readthedocs.io/en/latest/usage.html#batch-mode-default], and sets up your new project with some default values. Later, you may wish to case you need to run it in Wizard mode [https://djangocms-installer.readthedocs.io/en/latest/usage.html#wizard-mode]. The default in Batch mode is to set up an English-only project, which will be sufficient introduce Placeholders, and we’re also going to show how you can make your own HTML templates CMS-ready. 2.1. Templates You can use HTML templates to customise the look of your website, define Placeholders to

higher • django-mptt 0.5.2 (strict due to API compatibility 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 installing the django CMS using pip, Django, django-mptt django-classy-tags, django-sekizai, south and html5lib will be installed automatically. Recommended These packages are not required, but they provide but if you want to lock-in their version, specif Django==1.5.1 django-classy-tags==0.4 South==0.8.1 html5lib==1.0b1 django-mptt==0.5.2 django-sekizai==0.7 six==1.3.0 #Optional, recommended packages Pillow==2

introduce Placeholders, and we’re also going to show how you can make your own HTML templates CMS-ready. Templates You can use HTML templates to customise the look of your website, define Placeholders to mark the automatically-created home page’s template, it’s feature.html. Placeholders Placeholders are an easy way to define sections in an HTML template that will be filled with content from the database when using django CMS’s frontend editing mechanism, using Django templatetags. You can see them in feature.html: {% placeholder "feature" %} and {% placeholder "content" %}. You’ll also see {% load cms_tags %}

doing all of the following steps in a virtual environment [https://docs.python.org/3/library/venv.html]. You ought to know how to create, activate and dispose of virtual environments. If you don’t, you LICENSE README.md db.sqlite3 myproject/ static/ templates/ base.html __init__.py asgi.py settings.py urls.py wsgi.py manage project’s default template. In the root of the project, create a templates directory, and in that, home.html, a minimal django CMS template: from django.conf.urls.i18n import i18n_patterns from django.urls

higher • django-mptt 0.5.2 (strict due to API compatibility issues) • django-sekizai 0.6.1 or higher • html5lib 0.90 or higher • An installed and working instance of one of the databases listed in the Databases installing the django CMS using pip, Django, django-mptt django-classy-tags, django-sekizai, south and html5lib will be installed automatically. Recommended • django-filer with its django CMS plugins, file PageSelectWidget correctly orders pages again. • Fixed the file plugin which was sometimes causing invalid HTML (unclosed span tag). • Migration ordering for plugins improved. • Internationalized strings in JavaScript

django-classy-tags 0.3.4.1 or higher • django-mptt 0.4.2 or higher • django-sekizai 0.4.2 or higher • html5lib 0.90 or higher • An installed and working instance of one of the databases listed in the Databases installing the django CMS using pip, Django, django-mptt django-classy-tags, django-sekizai, south and html5lib will be installed automatically. Recommended • django-filer with its django CMS plugins, file tag library in your templates. The template tag should be placed somewhere within the body of the HTML (within ...). This solves issues people where having with the toolbar showing up in places