Django-perf-rec

Latest version: v4.25.0

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

Scan your dependencies

Page 5 of 8

4.7.0

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

* Add Django 3.1 support.

4.6.1

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

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

4.6.0

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

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

4.5.0

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

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

4.4.0

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

* Normalize SQL whitespace. This will change fingerprinted SQL in some cases.

4.3.0

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

* Add support for Django 2.2.

Page 5 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.