Remove Jingo requirement

[davedash]

I don't think Jingo is entirely required, but things like calling JINJA_CONFIG() make that hard... not sure what the best solution here is.

For a starter making JINJA_CONFIG optionally callable might be nice.

[fwenzel]

Makes sense, generally. What do you mean with "making JINJA_CONFIG optionally callable"? doesn't it already have to be a callable for tower to work? If anything, the syntax where JINJA_CONFIG isn't a callable doesn't currently work. Right?

[clouserw]

We could try/catch around it and have sensible defaults

[davedash]

For example JINGO_CONFIG = dict() is valid for jingo, since jingo checks to see if JINGO_CONFIG is just a setting or a callable, if it's a callable it calls it.

We could use that same logic.

But I think also the idea of using some sensible defaults makes sense. We should see what those coffin folks do.

Meanwhile I'll just adopt this syntax :)