Django-perf-rec

Latest version: v4.28.0

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

Scan your dependencies

Page 4 of 9

4.14.1

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

* Support arbitrary collections of keys being passed to Django cache operations.
Previously only mappings and sequences were supported, now sets and mapping
views will also work.

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

4.14.0

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

* Re-add simplification of SQL ``IN`` clauses to always use ``(...)``. This was
done in 4.6.0 but accidentally reverted with the sqlparse upgrade in 4.8.0.

Thanks to Dan Palmer for the report in
`Issue 373 <https://github.com/adamchainz/django-perf-rec/pull/373>`__.

4.13.1

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

* Fix SQL simplication for ``UPDATE`` queries without a ``WHERE`` clause.

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

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

Page 4 of 9

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.