Gapipy

-------------------

* Add ``contact_us`` field to the ``AgenchChain`` resource. This field can be
``None``, however should a value be present, it will be an object with three
accessible attributes: ``email``, ``phone_number``, and ``website_url``. See
the `PR 141`_ for more details.

.. _`PR 141`: https://github.com/gadventures/gapipy/pull/141

-------------------

* Add new ``Client`` configuration value that will raise an error when an empty
partial update (PATCH) payload is computed by gapipy. See `Issue 136`_ and
the corresponding `PR 137`_ for more details.

* The new Client configuration kwarg is ``raise_on_empty_update``, whose
default value is ``False``, and can also be set by passing it as an
environment variable ``GAPI_CLIENT_RAISE_ON_EMPTY_UPDATE``. If this config
value is set, then a call to ``Resource.save`` with ``partial=True`` will
raise the new ``EmptyPartialUpdateError`` if an empty payload is computed.

.. code-block:: python

from gapipy import Client

gapi = Client(application_key="your_api_key", raise_on_empty_update=True)
departure_service = gapi.departure_services.get(123456)

we've changed nothing and are calling a partial save (PATCH)

NOTE: the new EmptyPartialUpdateError will be raised here
departure_service.save(partial=True)

.. _`Issue 136`: https://github.com/gadventures/gapipy/issues/136
.. _`PR 137`: https://github.com/gadventures/gapipy/pull/137

-------------------

* Add ``travel_ready_policy`` model field to the ``Departure`` resource.
* More details can be found in our developer documentation.
c.f. `Departure travel-ready-policy`_

.. _`Departure travel-ready-policy`: https://developers.gadventures.com/docs/departure.html#travel-ready-policy

-------------------

* Add ``online_preferences`` field to the ``Agency Chain`` resource.

-------------------

* Make ``future`` requirement more flexible. See `PR 134`_ for more details.

.. _`PR 134`: https://github.com/gadventures/gapipy/pull/134

-------------------

* Initialize the ``DjangoCache`` via the ``BaseCache`` which exposes the
``default_timeout`` attribute to the class. Prior to this change, when using
the ``DjangoCache``, items would persist forever as no timeout would be set
on the entries. See `PR 133`_ for more details.

.. note:: ``DjangoCache`` was introduced in `2.30.0 (2021-02-08)`_

.. _`PR 133`: https://github.com/gadventures/gapipy/pull/133