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 1.8 support out of the box.
  
  
  === Django 1.8 support
  
  Django 1.8 introduces multiple template engines support and comes with Jinja2 backend.
  
  But it has some drawbacks:
  
  - not autoloads template tags.
  - by default search templates on _jinja2_ directory instead of _templates_ (jinja2 are also templates,
    I don't understand why put them in different directory?)
  - not setups i18n support.
  - not has support for django context processors.
  
  In summary, for make it working like _django_jinja_ is already working for years, it requires a lot
  of boilerplate.
  
  *django-jinja since version 1.1 also comes with django 1.8 compatible backend*, but supporting all
  the things.
  
  
  == Requirements
  
negative.code:                 "django.template.context_processors.tz",
                  "django.contrib.messages.context_processors.messages",
              ],
              "tests": {
                  "mytest": "path.to.tests.mytestfn",
              },
              "filters": {
                  "myfilter": "path.to.filters.myfilterfn",
              },
              "constants": {
                  "hello": "hello world",
              },
              "globals": {
                  "somefn": "path.to.functions.somefn",
              },
              "replace_filters_from_django": True,
              "extensions": [
                  "jinja2.ext.do",
                  "jinja2.ext.loopcontrols",
  