Fixed issue 57, order of middleware classes
Merge pull request #58 from evildmp/issue_57_docs

Fixed issue #57, order of middleware classes
+ add HTML_MIN_PARSER settings
Merge pull request #59 from Mystic-Mirage/master

+ add HTML_MIN_PARSER settings
setup: do not require django

Ignore the name.
bump to 0.6.3
Pin Django version for nosedjango compatibility

Until nosedjango works with Django 1.6, this is the simplest fix.
Django 1.6 requires a CACHE key in settings

This is just future proofing – if tests are to ever run with Django 1.6,
this needs to be present.
Add tests for between_two_tags

util is now at 100% coverage
Only process response if the request reached htmlmin
Extend RequestMock, add RequestBareMock w/o flag

RequestMock always pretends that htmlmin has seen the request, so
all other tests work normally.
Add tests for request flag
Fix test name
Merge pull request #62 from moeffju/feature/fix-travis-temp

Fix Travis build / fix tests (temporary fix)
Merge pull request #61 from moeffju/feature/minify-only-requested

Only process response if the request reached htmlmin
Split middleware into two to accommodate Django's ordering issues

Django calls middlewares top-down during a request and stops at the
first one that handles the request. In the response phase, *all*
middlewares are called. So we need to *mark* the request after
FetchFromCacheMiddleware has run, giving it a chance to return the
cached content (then our mark will never be set), and we need to check
if we should minify before UpdateCacheMiddleware runs, so we can minify
the response before caching.
Fix middleware and illustrate middleware order
Add test for entities within textarea
Make test pass

User input should never simply be unescaped. In this case, it could
enable XSS attacks if you put escaped tags into a textarea, because
upon minifying they would be unescaped.
Fix test name (since the underlying behavior changed)

The new behavior is correct according to HTML5 parsing and serialization
rules. A <textarea> can not contain other elements, if it does, that is
an error and the result should try to match the user’s intent. So, like
most browsers, HTML inside a <textarea> is properly escaped upon
parsing.