Django-recurrence

-----

* Fix for using the recurrence widget in admin inlines 137.

-----

* Minor fix for Django 2.0 134;
* Minor packaging fix 135.

-----

* Bad release, do not use.

-----

This release contains two backwards incompatible changes -
please read the notes below for details.

* django-recurrence now returns timezone aware ``datetime`` objects
in most cases 130. If ``USE_TZ`` is ``True`` (it
defaults to off with a stock Django install) then you'll now get
timezone aware ``datetime`` objects back from django-recurrence. If
you have ``USE_TZ`` as ``True``, and you don't want this behaviour,
you can set ``RECURRENCE_USE_TZ`` to ``False``, but please let us
know (via GitHub issues) that you wanted to opt out, so we can
understand what your use case is.
* ``RecurrenceField`` instances without ``required=False`` will now
require at least one rule or date. This change is intended to bring
django-recurrence into line with how custom fields should
behave. If you don't want to require at least one rule or date,
just set ``require=False`` on your field 133.
* Improvements to avoid inline styles 85;
* Handle changes to ``javascript_catalog`` in Django 2 131.

-----

* Drop official support for Django versions 1.7, 1.8, 1.9, 1.10;
* Fixes for saving ``None`` into a ``RecurrenceField`` causing a
``TypeError`` 89`, 122;
* Drop official support for Python 3.3 and Python 3.4;
* Provisional support for Python 3.7 (only for Django 2.0 and up);
* Ensure use of ``render`` on Django widgets always passes the
``renderer`` argument, to ensure support for Django 2.1 125;
* Django 2.0 compatibility fix for usage of django-recurrence with
Django REST framework 126.

-----

* Fixes for Python 3 105;
* Support for Django 2.0 109, 110;
* Switch back a couple of instances of ``DeserializationError`` to
``ValidationError`` 111;
* Switch around how we set dates in the date selector widget to avoid
issues with short months 113.