Django-perf-rec

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

* Support Python 3.9.
* Allow recording of tracebacks alongside db queries or cache operations,
selected via a function passed as ``capture_traceback`` to ``record()``.

Thanks to Nadege Michel in
`PR 299 <https://github.com/adamchainz/django-perf-rec/pull/299>`__.

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

* Drop Django 2.0 and 2.1 support.
* Upgrade for sqlparse 0.4.0+. This required changing how SQL lists of one
element are simplified, e.g. ``IN (1)`` will now be simplified to ``IN ()``
instead of ``IN (...)``. You should regenerate your performance record files
to match.

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

* Add Django 3.1 support.

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

* Create YAML files as non-executable. This will not be applied to existing
files, modify their permissions if necessary, or delete and recreate.

Thanks to Peter Law for the report in `Issue 264
<https://github.com/adamchainz/django-perf-rec/issues/264>`__.

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

* Drop Django 1.11 support. Only Django 2.0+ is supported now.
* Simplify SQL ``IN`` clauses to always use ``(...)``. Now ``x IN (1)`` and
``x IN (1,2)`` both simplify to ``x IN (...)``.

Thanks to Dan Palmer in
`PR 263 <https://github.com/adamchainz/django-perf-rec/pull/263>`__.

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

* Update Python support to 3.5-3.8, as 3.4 has reached its end of life.
* Converted setuptools metadata to configuration file. This meant removing the
``__version__`` attribute from the package. If you want to inspect the
installed version, use
``importlib.metadata.version("django-perf-rec")``
(`docs <https://docs.python.org/3.8/library/importlib.metadata.html#distribution-versions>`__ /
`backport <https://pypi.org/project/importlib-metadata/>`__).
* Fix ``Q()`` Patchy patch for Django 2.0+ with non-ANDed ``Q()``'s.