anchor.diff:  
   [WARNING]
   ====
  -This plugin is deprecated, *django-pipeline* is coming with good jinja support and it
  +This plugin is deprecated, *django-pipeline* is come with good jinja support and it
   should be used.
   
   You can use the native *django-pipeline* suport for jinja templates adding the
  
positive.code:                 "django.template.context_processors.tz",
                  "django.contrib.messages.context_processors.messages",
              ],
              "extensions": [
                  "jinja2.ext.do",
                  "jinja2.ext.loopcontrols",
  
negative.code: - Django 1.8 support out of the box.
  
  
  === Django 1.8 support notes
  
  
  Since django 1.8, multiple template engine support was added to django, and *django-jinja* comes
  with support for it. Implementing the backend interface and new configuration syntax.
  
  Django also comes with basic jinja backend, but it not has a lot of facilities and integrations
  with the rest of django. *django-jinja* comes to the rescue and add everything missing.
  
  *django-jinja* comes with that brief list of differences with django's built-in backend.
  
  * find the templates as usual in `"<appname>/templates"` directory instead of
    `"<appname>/jinja2"` directory.
  * preload template tags
  * gettext message loading (i18n)
  * support for django context processors
  
  NOTE: the usage of context processors is not the recommended way anymore, and with *django-jinja*
  you can done it setting global data or global constants. See below, in the django 1.8 configuration
  related section.
  
  
  == Requirements
  