Fix Deprecation warning in Django 1.9

[jieter]

about first param to template.render:

[...]bootstrap3/utils.py:142: RemovedInDjango110Warning: render() must be called with a dict, not a Context.
  return template.render(Context(context))

Fixes #279 and #290

[jieter]

Hmm, I see I need to run the tests locally to see what's wrong, I only copied the patch which made the warnings go away, but didn't run the tests on it... Hang on.

[jieter]

Hmm, this is more complicated than I anticipated. It turns out templates returned from get_template() do not the context arg as a Context object, but removing all wrapping in Context yields errors here.

Got it fixed for django 1.8/1.9 now, other versions still fail.

[nikolas]

I think django-bootstrap3 should discontinue support for at least django versions 1.4-1.6, since these are no longer supported by the django project.

[dyve]

I agree, but I still have 1 project on 1.6 myself, so I'm postponing dropping 1.6 support until that one is migrated (should be soon).

[dyve]

For now, CI related pull requests should have passing Travis tests, so I am not pulling this in.

[troygrosfield]

@jieter, why doesn't the code just do something along the lines of:

if django.VERSION >= (1, 9):
    # do django 1.9 and up stuff

That makes the change passive with older django versions and removes the deprecation warning from django 1.9 and up.

[jieter]

@troygrosfield yeah, that'll work. I did that for django-tables2

[dyve]

Fix is in place now in develop branch, but I think it's ugly. Improvements welcome, as long as tests pass (keep Travis and tox happy).

[jieter]

pff, PITA

[dyve]

I dropped support for Django < 1.8 and python < 2.7 for this issue amongst others, so maybe that'll help. I strongly suspect a bug in Django that makes some templates still require Context.