Django-cachalot

-----

- Adds support for ``.union``, ``.intersection`` & ``.difference``
that should have been introduced since 1.5.0
- Fixes error raised in some rare and undetermined cases, when the cache
backend doesn’t yield data as expected

-----

- Allows specifying a schema name in ``Model._meta.db_table``

-----

- Adds Django 2.0 support
- Drops Django 1.10 support
- Drops Django 1.8 support (1.9 support was dropped in 1.5.0)
- Adds a check to make sure it is used with a supported Django version
- Fixes a bug partially breaking django-cachalot when an error occurred during
the end of a `transaction.atomic` block,
typically when using deferred constraints

-----

- Adds Django 1.11 support
- Adds Python 3.6 support
- Drops Django 1.9 support (but 1.8 is still supported)
- Drops Python 3.3 support
- Adds ``CACHALOT_DATABASES`` to specify which databases have django-cachalot
enabled (by default, only supported databases are enabled)
- Stops advising users to dynamically override cachalot settings as it cannot
be thread-safe due to Django’s internals
- Invalidates tables after raw ``CREATE``, ``ALTER`` & ``DROP`` SQL queries
- Allows specifying model lookups like ``auth.User`` in the API functions
(previously, it could only be done in the Django template tag, not in the
Jinja2 ``get_last_invalidation`` function nor in API functions)
- Fixes the cache used by ``CachalotPanel`` if ``CACHALOT_CACHE`` is different
from ``'default'``
- Uploads a wheel distribution of this package to PyPI starting now,
in addition of the source release
- Improves tests

-----

- Fixes a circular import occurring when CachalotPanel is used
and django-debug-toolbar is before django-cachalot in ``INSTALLED_APPS``
- Stops checking compatibility for caches other than ``CACHALOT_CACHE``

-----

- Fixes a bad design: ``QuerySet.select_for_update`` was cached, but it’s not
correct since it does not lock data in the database once data was cached,
leading to the database lock being useless in some cases
- Stops automatically invalidating other caches than ``CACHALOT_CACHE`` for
consistency, performance, and usefulness reasons
- Fixes a minor issue: the ``post_invalidation`` signal was sent during
transactions when calling the ``invalidate`` command
- Creates `a gitter chat room <https://gitter.im/django-cachalot/Lobby>`_
- Removes the Slack team. Slack does not allow public chat, this was therefore
a bad idea