Django-perf-rec

Latest version: v4.25.0

Safety actively analyzes 629599 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 8

4.13.0

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

* Stop distributing tests to reduce package size. Tests are not intended to be
run outside of the tox setup in the repository. Repackagers can use GitHub's
tarballs per tag.

* Add support for hiding some operations from being recorded, via a new
``capture_operation`` callable to ``record``. This is potentially useful where
a different backend is used in testing than would be used in production and
thus a portion of the operations in a context are not representative.

Thanks to Peter Law in
`PR 342 <https://github.com/adamchainz/django-perf-rec/pull/342>`__.

4.12.0

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

* Support Django 3.2.

4.11.0

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

* Drop Python 3.5 support.
* Remove ORM patching. Now that only Python 3.6 is supported, the
insertion-order of ``dict``\s should mean Django's ORM always provides
deterministic queries. The two patches django-perf-rec made on the ORM have
been removed, and the corresponding dependency on patchy. You may need to
regenerate your performance record files.

This fixes an issue where use of ``annotate()`` with dependencies between the
annotations could cause a query error after django-perf-rec sorted the
annotation names.

Thanks to Gordon Wrigley for the report in
`Issue 322 <https://github.com/adamchainz/django-perf-rec/issues/322>`__.

4.10.0

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

* Correctly record calls to ``cache.get_or_set()``.

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

4.9.0

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

* 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>`__.

4.8.0

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

* 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.

Page 4 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.