Django-perf-rec

Latest version: v4.25.0

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

Scan your dependencies

Page 7 of 8

2.2.0

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

* Use ``kwargs-only`` library rather than vendored copy.
* Erase volatile part of PostgreSQL cursor name.

2.1.0

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

* Exposed the automatic naming logic used in ``record()`` in two new functions
``get_perf_path()`` and ``get_record_name()``, in order to ease creation of
test records from calls outside of tests.
* Made the automatic test detection work when running under a Pytest fixture.
* Stopped throwing warnings on Python 3.
* Fixed loading empty performance record files.

2.0.1

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

* Make cascaded delete queries deterministic on Django <1.10, with another
Patchy patch to make it match the order from 1.10+.

2.0.0

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

* Arguments to ``record`` must be passed as keyword arguments.
* ``file_name`` is removed as an argument to ``record`` following its
deprecation in release 1.1.0.

1.1.1

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

* Fix django session keys not being fingerprinted.
* Show diff when records don't match (when not on pytest).
* Add new 'MODE' setting with three modes. This allows customization of the
behaviour for missing performance records. The new ``'none'`` mode is
particularly useful for CI servers as it makes tests fail if their
corresponding performance records have not been committed.

1.1.0

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

* Fix automatic filenames for tests in ``.pyc`` files.
* Add the ``path`` argument to ``record`` which allows specifying a relative
directory or filename to use. This deprecates the ``file_name`` argument,
which will be removed in a future major release. For more info see the
README.

Page 7 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.